Skip to main content
Glama
qobuz-mcp
by cheubes

List Featured Albums

list_featured_albums
Read-only

Browse Qobuz editorial album lists such as new releases, editor picks, or best sellers, with optional genre filtering and pagination to review the catalog's curated selections.

Instructions

List albums from one of Qobuz's editorial selections, optionally for one genre.

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": {
      "category": "<category>"
    },
    "name": "list_featured_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
categoryYesEditorial list: new releases, press awards, best sellers, most streamed, editor picks, ideal discography, Qobuzissimes, album of the week, or a label selection.
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

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 only the notion that results come from a curated editorial source; it says nothing about pagination behavior or result ordering that the annotations do not cover.

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?

A single sentence with the verb and scope front-loaded and zero filler. Nothing could be removed without losing meaning.

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, full parameter documentation, and annotations, the description covers what the agent needs to invoke it correctly. It is slightly thin on routing guidance against the many sibling list/search tools, but no functional detail is missing.

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%, so category, genre_id, limit, and offset are fully documented in the schema itself. The description's "optionally for one genre" merely restates the genre_id parameter and adds no format or constraint detail beyond it — baseline 3.

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?

The description gives a specific verb and resource ("List albums") plus a clear scope ("from one of Qobuz's editorial selections"). It implicitly separates this from playlist-oriented siblings by naming albums, but never names an actual alternative, so differentiation is left to the reader.

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?

Usage is only implied: browse editorial/curated album lists, optionally narrowed by genre. There is no statement of when to prefer this over search_catalog, list_awards, or list_new_releases_from_favorites, and no exclusions or prerequisites.

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