Skip to main content
Glama
qobuz-mcp
by cheubes

Get Album

get_album
Read-only

Retrieve detailed album information including tracklist, audio quality, artists, label, genre, and release date. Paginate tracks with limit and offset to handle large albums.

Instructions

Get an album's details: tracklist, audio quality, artists and roles, label, genre, release date, description, press awards and booklet links.

The tracklist is paginated with limit and offset; tracks.has_more tells whether more tracks exist.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
album_idYesQobuz album ID (a string).

Output Schema

NameRequiredDescriptionDefault
idYes
upcYes
urlYes
genreYes
labelYes
titleYes
artistYes
awardsYes
tracksYes
artistsYes
versionYes
bookletsYes
composerYes
copyrightYes
streamableYes
descriptionYes
release_dateYes
release_typeYes
tracks_countYes
audio_qualityYes
duration_secondsYes
parental_warningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 non-obvious behavior: pagination applies to the tracklist specifically, and tracks.has_more is the signal for further pages. It stops short of covering rate limits, auth needs, or response shape, which keeps it below a 5.

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 tight paragraphs with zero filler: the payload contents are front-loaded, then pagination semantics. Every sentence carries information an agent would otherwise have to guess.

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-value detail is not strictly required, and the safety profile is annotation-covered. The remaining small gap is that it never says where an album_id comes from or what a failed lookup looks like, but for a read-by-ID tool this is close to complete.

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 coverage is 100%, so baseline is 3. The description goes beyond it by scoping limit/offset to the tracklist rather than the whole response and by explaining that tracks.has_more indicates additional pages, which the schema does not convey.

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 states a specific verb and resource ('Get an album's details') and enumerates exactly what comes back: tracklist, audio quality, artists and roles, label, genre, release date, description, awards, booklet links. That makes it clearly distinct from get_track or get_artist by resource scope, though it never explicitly names a sibling to contrast with.

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: fetch album metadata by ID. The second paragraph explains pagination mechanics but not when to choose this tool over get_track, search_catalog, or list_similar_albums, and gives no prerequisites or exclusions.

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