Skip to main content
Glama
qobuz-mcp
by cheubes

Get Label

get_label
Read-only

Retrieve a record label's description and its albums by label ID, using limit and offset pagination to browse more results.

Instructions

Get a record label's description and its albums.

The albums are paginated with limit and offset; albums.has_more tells whether more albums 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": {
      "label_id": "<label_id>"
    },
    "name": "get_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
label_idYesQobuz label ID (an integer).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
albumsYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 pagination contract and the albums.has_more flag, which is useful behavioral context. It does not mention error behavior for an invalid label_id or the shape of the label metadata.

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?

The description is two short sentences, front-loaded with what the tool returns, followed by the pagination detail. Nearly every phrase earns its place, with only a small amount of overlap with the schema on limit and offset.

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 the description does not need to enumerate return values, and the annotations cover the read-only profile. The description covers the resource, the two parts of the result, and pagination. Only sibling disambiguation is missing for a complex catalog.

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%, so label_id, limit, and offset are already documented at the field level. The description repeats the pagination meaning of limit and offset and points to albums.has_more. That is marginal value beyond the schema, consistent with the baseline of 3.

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 names a specific verb and resource: 'Get a record label's description and its albums.' That tells an agent exactly what is returned. It does not differentiate from look-alike siblings such as list_label_items, so it falls 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 required label_id: fetch a label's detail and album list. The description never states when to choose this over list_label_items or how to handle a missing label. The pagination notes address mechanics, not when-to-use.

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