Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer track

deezer_track_get
Read-onlyIdempotent

Retrieves a Deezer track by ID with credits, copyright, rights, available countries, other releases, and a 30-second preview link.

Instructions

Get a Deezer track with its credits, copyright, rights, countries, other releases and a 30 second preview link. Requires trackId.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
trackIdYesRequired. Deezer track id, for example `3135556`.
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.5/5.0
Behavior4/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 real value on top by telling the agent what payload comes back (credits, copyright, rights, countries, other releases, 30s preview) in the absence of an output schema. It omits any note on rate limits or upstream failure modes, keeping it short of a 5.

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?

A single front-loaded sentence naming the resource and its payload, followed by a short requirement clause. No boilerplate, no redundancy. It is lean rather than padded; the only reason it is not a 5 is that the trailing 'Requires `trackId`' duplicates what the schema already marks as required.

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 simple read-only lookup with full schema coverage and rich annotations, the description covers the essential question an agent has: what do I get back. The absence of an output schema makes the field enumeration especially load-bearing, and it is present. It stops short of explaining when the multi-call conversation_id handshake matters, but that is documented in the schema itself.

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 all five parameters carry their own descriptions, including the trackId pattern example and the context/conversation_id conventions, so the schema does the heavy lifting. The description says nothing about the non-obvious bookkeeping parameters (context, llm_model, conversation_id) beyond echoing the trackId requirement, which is acceptable at baseline but adds no meaning.

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 ('Get a Deezer track') and enumerates exactly what the response carries: credits, copyright, rights, countries, other releases, and a 30-second preview. That is far more than a restated title. It does not, however, distinguish itself from near-neighbours such as deezer_track_by_isrc_get, deezer_tracks_batch_get, or deezer_track_lyrics_get, so an agent must reason about which track-lookup to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only usage signal is 'Requires `trackId`', which merely restates a required schema field. There is no statement of when to prefer this over the by-ISRC variant, the batch endpoint, or the lyrics endpoint, and no exclusions or prerequisites beyond the parameter requirement.

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