Skip to main content
Glama
qobuz-mcp
by cheubes

Suggest Tracks

suggest_tracks
Read-only

Generate track suggestions to continue a playlist from 1–10 seed track IDs, excluding the given tracks and returning one page up to the requested limit.

Instructions

Suggest tracks to continue a list of tracks, for example to extend a playlist.

The given tracks are never suggested. The result is one complete page of up to limit tracks, with no further pages.

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": {
      "track_ids": "<track_ids>"
    },
    "name": "suggest_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
track_idsYes1 to 10 Qobuz track IDs to continue, such as the end of a playlist.

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/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 two genuinely useful behavioral facts beyond that: seed tracks are excluded from results, and the response is a single complete page with no further pages. It does not explain what the suggestions are based on (similarity model, popularity, etc.), which for an open-world recommender would be informative.

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?

Three short sentences, front-loaded with purpose, then two constraints. Every sentence carries information an agent would otherwise have to guess.

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

Completeness4/5

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

Low-complexity tool with two parameters, a full output schema, and read-only annotations, so the description covers the essentials: what it returns, that seeds are excluded, and that there is no next page. The only gap is that it does not characterize the basis or quality of the recommendations.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns above that by explaining that track_ids seeds are excluded from output and that limit defines one complete page with no pagination follow-up. That adds operational meaning ('do not loop on limit') not present in the schema.

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

Purpose4/5

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

States a specific verb and resource ('Suggest tracks') plus a concrete use case ('continue a list of tracks, for example to extend a playlist'), which separates it from catalog search or playlist-mutation siblings. It does not name an explicit alternative, but the recommendation framing is distinctive enough to route correctly.

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?

Gives clear when-to-use context: extending a playlist or continuing a sequence of tracks. It also bounds behavior ('the given tracks are never suggested'), which is a useful negative constraint, but it never names a sibling to use instead when the agent wants seed-based search or similar-artist expansion.

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