Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer artist releases

deezer_artist_albums_list
Read-onlyIdempotent

Retrieve a Deezer artist's albums, EPs, singles, or featured appearances by artist ID, with filters for release type and sort order plus cursor pagination.

Instructions

List a Deezer artist's releases or appearances. Requires artistId. Returns a list (use cursor when paginated).

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": {
      "artistId": "<artistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_artist_albums_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo`main` (default) lists the artist's own releases; `featured` lists releases they appear on.
sortNoOrder of the list. Default: `newest`.
limitNoItems per page, 1 to 500. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
subTypeNoOnly releases of this kind.
artistIdYesRequired. Deezer artist id, for example `27`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
recordTypeNoOnly releases of this type.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
includeNonOfficialNoAlso list releases that are not official artist releases but credit the artist. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds the pagination/return-shape note, which is useful, but does not mention the `conversation_id` sequencing rule or the `includeNonOfficial`/`role` behavior that materially changes what comes back.

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?

Three short sentences with the prerequisite and the pagination caveat front-loaded; nothing is padded. The middle sentence ('Returns a list') is slightly redundant since the name already says 'list', but it sets up the cursor hint efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with no output schema, the description is thin: it never explains the default release set, how `role`/`includeNonOfficial` interact, or what a page object looks like beyond the cursor field. The rich schema carries most of the weight, which keeps this at minimum-viable rather than failing.

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. The description restates `artistId` and the cursor mechanic, both fully documented in the schema, and adds nothing about `role`, `subType`, `recordType`, or `sort` semantics that isn't already there.

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 a Deezer artist's releases or appearances.' An agent can distinguish this from album-level or track-level siblings. It does not name a sibling alternative, but the resource boundary (artist-scoped release catalog) is clear.

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?

Gives the hard prerequisite ('Requires `artistId`') and a pagination hint ('use cursor when paginated'), which is real operational guidance. But it never says when to pick this over `deezer_artist_playlists_list`, `deezer_artist_top_tracks_list`, or `deezer_artist_get`, so the routing decision is left to inference.

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

Deploy Server

Other Tools