Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer album

deezer_album_get
Read-onlyIdempotent

Retrieve a Deezer album by ID to access its label, barcode, copyright lines, credits, and full track list.

Instructions

Get a Deezer album with its label, barcode, copyright lines, credits and every track. Requires albumId.

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

Input Schema

NameRequiredDescriptionDefault
albumIdYesRequired. Deezer album id, for example `302127`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoTwo-letter language code for editorial text, such as `fr`. Titles and names are not translated. Default: `en`.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful scope information ('every track', credits, copyright lines) implying a full, possibly large payload, but says nothing about rate limits, pagination of the track list, or auth/availability constraints.

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, front-loaded with the resource and its returned contents, followed by the hard requirement. Nothing extraneous.

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 five parameters all fully documented in schema and no output schema, the description responsibly sketches the response shape (label, barcode, copyright, credits, all tracks). It could say more about payload size or whether the track list is complete/paginated, but nothing an agent needs to invoke it correctly is missing.

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 every parameter is documented in-schema with format examples, so the schema carries the burden. The description only restates that `albumId` is required and adds no meaning about `language`, `context`, or the conversation_id handshake.

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 (Get) and resource (Deezer album) and enumerates the returned fields (label, barcode, copyright lines, credits, tracks), plus the key input ('Requires albumId'). This implicitly separates it from deezer_album_by_upc_get (id vs UPC lookup), though it never names that distinction explicitly.

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: the id-based lookup and required `albumId` suggest when this tool applies, but there is no explicit statement of when to prefer it over deezer_album_by_upc_get, deezer_album_get_batch, or cross-provider album tools. No exclusions or prerequisites beyond the required parameter.

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