Skip to main content
Glama
qobuz-mcp
by cheubes

Get Radio

get_radio
Read-only

Retrieve a fixed list of up to 30 Qobuz radio tracks seeded from an album, artist, or track to browse related music without pagination.

Instructions

Get the tracks of a radio built by Qobuz from an album, an artist or a track.

Qobuz returns one fixed list of up to 30 tracks, with no further pages. Use suggest_tracks instead to continue a list of tracks, such as a playlist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seed_type": "<seed_type>",
      "seed_id": "<seed_id>"
    },
    "name": "get_radio"
  }
}

Input Schema

NameRequiredDescriptionDefault
seed_idYesQobuz ID of the seed: an album ID, or an artist or track ID in digits.
seed_typeYesWhat the radio is built from.

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the non-obvious behavioral fact that Qobuz returns exactly one fixed list of up to 30 tracks with no further pages, which materially affects how an agent plans calls. It stops short of describing error behavior for invalid or unknown seed IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both load-bearing: the first establishes purpose and seed scope, the second delivers the pagination limit and the sibling routing. The most decision-relevant constraint (no further pages) is front-loaded in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with annotations and an output schema present, the description supplies everything an agent needs: the seed semantics, the 30-track cap, the absence of pagination, and the redirect for continuation use cases. Return shape is correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both seed_id and seed_type documented, including the enum values. The description's mention of 'an album, an artist or a track' restates the enum rather than adding format or constraint detail, so the schema is doing the semantic work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('get the tracks of a radio built by Qobuz') and enumerates the three seed types (album, artist, track). It also implicitly separates itself from the sibling suggest_tracks, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names an explicit alternative and the condition that selects it: use suggest_tracks to continue a list of tracks such as a playlist. What is missing is a direct statement of when to prefer get_radio (e.g. when you want a one-shot discovery set for a seed), which is only inferable from the no-pagination note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.