Skip to main content
Glama
qobuz-mcp
by cheubes

Get Similar Artists

get_similar_artists
Read-only

Retrieve artists similar to a given Qobuz artist ID to discover new music, with paging controls to browse results in batches.

Instructions

List artists similar to a given artist, as Qobuz suggests them, to discover new music.

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": "get_similar_artists"
  }
}

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 does add one useful behavioral fact — that results are Qobuz's suggestions rather than a computed similarity metric, meaning ranking is opaque and not reproducible. It says nothing about empty results, invalid IDs, or pagination behavior, so the addition is modest rather than rich.

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 fifteen-word sentence that front-loads the verb and resource and ends with the motivating use case. Nothing is redundant or padded.

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 and all three parameters are documented, so return values and paging need no prose. For a simple read-only lookup the description covers what the tool is and why, missing only edge-case behavior such as what an unknown artist_id yields.

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 inline including ranges and defaults. The description adds no syntax or format detail beyond 'a given artist', 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 artists similar to a given artist' — and notes the results come from Qobuz's own suggestion engine, which distinguishes it from a generic similarity computation and implicitly from the sibling list_similar_albums. It stops short of explicitly naming a sibling it should be preferred over.

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?

'to discover new music' implies a discovery/browsing context, which is real but weak guidance. There is no statement of when to prefer this over search_catalog or get_artist, and no prerequisites (e.g., needing a valid artist ID first).

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