Skip to main content
Glama
qobuz-mcp
by cheubes

List Similar Albums

list_similar_albums
Read-only

Find albums similar to a specified Qobuz album using Qobuz recommendations. Provide an album ID to retrieve up to 30 related albums in one fixed list.

Instructions

List albums similar to a given album, as Qobuz recommends them.

Qobuz returns one fixed list of up to 30 albums, 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": {
      "album_id": "<album_id>"
    },
    "name": "list_similar_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYesQobuz album ID (a string).

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the list is fixed, capped at 30 albums, and has no further pages, which tells the agent not to attempt pagination or expect exhaustive results.

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, front-loaded with the action and immediately followed by the result-shape constraint. No filler, no restatement of the title, and every sentence contributes new 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?

Given an output schema, one documented parameter, and annotations covering the safety profile, the description supplies everything an agent needs to call it correctly, including the result cap and absence of paging. Only the routing guidance versus sibling tools 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?

There is a single parameter with 100% schema description coverage ('Qobuz album ID (a string)'), so the schema already carries the burden. The description adds no extra meaning about the album_id format, where to obtain it, or what happens with an invalid ID.

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 albums similar to a given album') plus the provenance of the result ('as Qobuz recommends them'), which separates it from generic listing siblings like list_featured_albums or get_album. It does not explicitly name an alternative, so it stops just 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?

Usage is only implied by the word 'similar' — an agent can infer this is a recommendation/discovery call rather than a lookup or search. There is no explicit statement of when to prefer it over search_catalog, get_album, or get_similar_artists, and no prerequisites mentioned.

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