Skip to main content
Glama
qobuz-mcp
by cheubes

List Featured Playlists

list_featured_playlists
Read-only

Browse Qobuz editorial playlists filtered by genre or tag, then open any playlist to view its tracks.

Instructions

List Qobuz's editorial playlists, optionally for one genre or one tag.

Use get_playlist to see a playlist's tracks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_featured_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly playlists with this tag: hi-res, new (new releases), focus, mood, artist, danslecasque (listening with...), label (label stories), qobuzdigs, event (events and media), auditoriums (hi-fi audio partners), speakers (test your speakers), ideal-discography, popular (top playlists).
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
genre_idNoOnly items of this genre (an ID from `list_genres`).

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 and reach profile is covered. The description adds only that the content is Qobuz-curated editorial material; it says nothing about ordering, page size behavior, or whether results are stable across calls, all of which would be valuable given the offset/limit parameters.

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, zero filler, with the primary purpose front-loaded and the follow-up routing placed second. Nothing redundant with the schema or annotations is repeated.

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-shape explanation is correctly omitted, and annotations cover the read-only profile. For a zero-required-parameter listing tool this is nearly complete; the only mild gap is that pagination semantics beyond what the schema states are not mentioned.

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 description coverage is 100%, so the baseline is 3, but the description adds a genuine semantic constraint by noting the genre/tag filters are mutually exclusive in spirit ('one genre or one tag') and that they are optional. It still doesn't explain that genre_id must come from `list_genres` — that lives in the schema only.

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?

States a specific verb and resource ('List Qobuz's editorial playlists') plus the optional scoping dimensions (one genre or one tag). The word 'editorial' plus the first-person distinction implicitly separates it from the sibling lists (list_my_playlists, list_artist_playlists, list_featured_albums), so an agent can pick it without opening the schema.

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?

It gives one concrete hand-off rule: use `get_playlist` to see a playlist's tracks, which correctly routes the follow-up call. However it gives no guidance on when to prefer this over other list tools (e.g. artist or personal playlists) and no exclusions or precondition notes.

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