Skip to main content
Glama
qobuz-mcp
by cheubes

Get Artist

get_artist
Read-only

Retrieve an artist's biography and discography by ID, newest releases first, with pagination and an option to return the full biography.

Instructions

Get an artist's biography and discography, newest releases first.

By default, biography is the start of the biography, at most 1,000 characters cut at a sentence end, and biography_truncated tells whether text was cut. Set full_biography when the user wants to know more about the artist: the full text can reach several thousand characters. The discography is paginated with limit and offset; albums.has_more tells whether more releases exist. Use get_similar_artists to discover related artists.

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_artist"
  }
}

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).
release_typeNoOnly releases of this type: album, live, compilation, epSingle (EPs and singles), other, awardedRelease (releases with a press award), next (upcoming releases). Omit for the whole discography.
full_biographyNoReturn the full biography, which can be long, not an excerpt.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
albumsYes
biographyYes
albums_countYes
biography_truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description supplies the behavior that actually matters here — default biography is truncated to at most 1,000 characters at a sentence boundary, `biography_truncated` signals cut text, and full text can run to several thousand characters. It also discloses pagination semantics for the discography. It stops short of describing error behavior for invalid artist IDs.

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?

Front-loaded with purpose, then parameter behavior, then the sibling redirect — a sensible order. Wording is tight, though the truncation explanation is somewhat elaborate relative to the rest.

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?

For a read-only lookup with five params, an output schema, and full schema coverage, the description covers the non-obvious parts: truncation, the `has_more` pagination signal, and the related-artist alternative. Return-value structure is left to the output schema, which is appropriate; only failure modes are unaddressed.

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 the baseline is 3, and the description mostly restates what the schema already documents for `limit`, `offset`, and `full_biography`. It adds marginal value by tying `full_biography` to an intent ('when the user wants to know more') and noting the resulting text size, but no new syntax or format detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get an artist's biography and discography') plus the ordering of results ('newest releases first'). It also names the sibling it is not, get_similar_artists, for related-artist lookups, so an agent can separate the two without opening either schema.

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?

Gives explicit conditional guidance: 'Set `full_biography` when the user wants to know more about the artist' and 'Use `get_similar_artists` to discover related artists.' Clear context and an explicit alternative, though it does not state exclusions such as when to prefer a search tool over fetching by ID.

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