Skip to main content
Glama
qobuz-mcp
by cheubes

Get Playlist

get_playlist
Read-only

Retrieve a Qobuz playlist’s details and paginated track entries, including each entry’s playlist_track_id for removing or moving tracks and its track ID for reference.

Instructions

Get a playlist's details and its entries, paginated with limit and offset.

Each entry has a playlist_track_id, which identifies that entry in the playlist (the same track can appear twice), and the track itself with its id. Removing or moving entries takes playlist_track_id values.

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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
playlist_idYesQobuz playlist ID (an integer).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
ownerYes
genresYes
entriesYes
is_publicYes
updated_atYes
descriptionYes
tracks_countYes
duration_secondsYes
is_collaborativeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 real behavioral context beyond that — pagination via limit/offset, the fact that the same track can appear twice, and the distinction between `playlist_track_id` and the track's `id`. It does not state what happens for an unknown or private playlist_id, which is the remaining gap for a read tool.

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

Conciseness4/5

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

Three sentences, front-loaded with the core action and payload. The final sentence is slightly tangential to this tool's own call (it describes how other tools consume the returned ID) but still earns its place by explaining why entry identity matters.

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?

With an output schema present, the description need not spell out return fields, and it correctly focuses on pagination and entry identity. It is nearly complete for a 3-parameter read tool; the only omissions are error/auth behavior and explicit sibling routing.

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 schema already documents limit (1–100), offset, and playlist_id. The description nonetheless adds meaning by framing limit/offset as pagination controls and by introducing `playlist_track_id` as an entry identity used by other endpoints, which the input schema alone does not convey.

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?

"Get a playlist's details and its entries" gives a specific verb and resource, and the follow-up clarifies the two-part payload (metadata plus entries). It never names a sibling such as list_my_playlists, so an agent must infer the distinction between fetching one playlist by ID and enumerating the user's playlists.

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

Usage Guidelines3/5

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

The closing sentence explains that removing or moving entries takes `playlist_track_id` values, which is genuinely useful for chaining into move_playlist_tracks/remove_tracks_from_playlist. However, it gives no guidance on when to call this versus list_my_playlists or get_track, and no prerequisites (e.g., private playlists requiring auth) are stated.

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