Skip to main content
Glama
qobuz-mcp
by cheubes

List Artist Playlists

list_artist_playlists
Read-only

Lists Qobuz editorial playlists that feature a specific artist, letting you browse curated collections by artist ID. Use it to find playlists showcasing an artist before fetching tracks from any playlist.

Instructions

List Qobuz's editorial playlists featuring an artist.

Use get_playlist to see a playlist's tracks.

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": {
      "artist_id": "<artist_id>"
    },
    "name": "list_artist_playlists"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

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 meaningful context that these are Qobuz editorial playlists rather than the user's own, but says nothing about result ordering, pagination behavior, or empty results beyond what the schema implies.

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 short sentences with zero waste: the purpose and scope come first, then a single actionable cross-reference. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description is adequate for a three-parameter read tool, though a note on pagination expectations or on what 'editorial' excludes would make it complete.

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 limit, offset, and artist_id all documented in the schema itself including ranges and defaults. The description adds no additional meaning about the parameters, so the baseline 3 applies.

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 ('List ... editorial playlists') and scopes it to 'featuring an artist', which is more precise than the bare name. It does not distinguish itself from sibling list tools such as list_my_playlists or list_featured_playlists, so it falls short of a 5.

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 description supplies a follow-up route ('Use get_playlist to see a playlist's tracks'), which is genuinely helpful, but it gives no explicit when-to-use versus when-not-to-use guidance and no alternatives for the same task. Usage is only implied by the 'editorial playlists featuring an artist' framing.

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