Skip to main content
Glama
qobuz-mcp
by cheubes

List Label Items

list_label_items
Read-only

List one section of a Qobuz record label—top artists, upcoming releases, playlists, or press-award releases—and paginate to browse the label's items.

Instructions

List one section of a record label: artists, albums or playlists, matching section.

Use get_label for the label's description and its whole catalog of albums.

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": {
      "label_id": "<label_id>",
      "section": "<section>"
    },
    "name": "list_label_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
sectionYesWhich part of the label: its top artists, its upcoming releases, its editorial playlists, or its releases that received a press award.
label_idYesQobuz label ID (an integer).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the partitioning behavior (only one section is returned per call, not the whole catalog), which is genuinely useful. It says nothing about pagination behavior or ordering, though the limit/offset schema and the output schema cover much of that.

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, zero waste, with the core scope stated first and the sibling routing second. Nothing is repeated from the schema or annotations.

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 a fully described 4-parameter schema, annotations, and an output schema, the description only needs to establish scope and routing, and it does both. The one small gap is that it doesn't clarify whether a single call can span sections or how results are ordered, but that is minor given the structured coverage.

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 enum for `section` is fully documented in the schema. The description restates the section semantics in looser prose ('artists, albums or playlists') without adding syntax, format, or labeling details beyond the schema. Baseline 3 is appropriate.

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 one section of a record label) and narrows scope to the `section` parameter. The second sentence names `get_label` as the tool for the label's description and full catalog, so an agent can distinguish the two without opening either schema. The summary 'artists, albums or playlists' is slightly looser than the actual enum values (top_artists, upcoming_releases, playlists, awarded_releases), which keeps it from 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 Guidelines4/5

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

Explicitly routes the agent: use this tool for a section, use `get_label` for the description and whole album catalog. That is a clear alternative with a condition. No explicit exclusions or prerequisites (e.g., label_id must come from a prior lookup) are stated, so it falls short of a 5.

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