Skip to main content
Glama
qobuz-mcp
by cheubes

Get Track

get_track
Read-only

Retrieve a Qobuz track’s performer, credits, composer, album, audio quality, ISRC, and release date using its track ID.

Instructions

Get a track's details: main performer, credits, composer, work, album, audio quality, ISRC and release date.

credits is Qobuz's own text listing every contributor with their roles.

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": {
      "track_id": "<track_id>"
    },
    "name": "get_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYesQobuz track ID (an integer).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
isrcYes
workYes
albumYes
titleYes
creditsYes
versionYes
composerYes
copyrightYes
performerYes
streamableYes
media_numberYes
release_dateYes
track_numberYes
audio_qualityYes
duration_secondsYes
parental_warningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral note: that `credits` is Qobuz's own free-text contributor listing rather than structured data, which prepares the agent for its shape. It says nothing about failure modes (invalid/unknown ID) or upstream rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the field inventory, then a single targeted clarification about `credits`. No filler, though the second sentence partially duplicates information the output schema likely already carries.

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?

This is a simple one-parameter read with an output schema, so the description does not need to explain return values; it does need to cover what it does and how it differs from neighbors, and it mostly does. The only real omission is routing guidance toward discovery tools when the agent lacks a track_id.

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% and the single parameter's schema entry already explains it is a Qobuz track ID integer. The description adds no format, range, or sourcing hints beyond that, 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?

The description gives a specific verb and resource ("Get a track's details") and enumerates the actual fields returned (performer, credits, composer, work, album, audio quality, ISRC, release date), which lets an agent tell this apart from album- or artist-level lookups. It stops short of naming a sibling alternative, keeping it at a clear-but-undifferentiated 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as search_catalog for discovering a track first. The required track_id parameter only weakly implies that an ID must already be known; that inference is left entirely to the agent.

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