Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer radio tracks

deezer_radio_tracks_list
Read-onlyIdempotent

Fetches about 25 tracks from a Deezer radio using its radio ID, returning a list for playback, discovery, or playlist building.

Instructions

Get about 25 tracks from a Deezer radio. Requires radioId. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
radioIdYesRequired. Deezer radio id from the radios list, for example `38305`.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the result is about 25 tracks — but says nothing about pagination, cursoring, or whether the count varies.

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, front-loaded with the action and the approximate result size. 'Requires `radioId`' duplicates the schema's 'Required.' note and is the only wasted clause.

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?

With no output schema, 'Returns a list' is thin — an agent learns nothing about track fields or whether the 25-item cap is fixed. Annotations plus full schema coverage carry most of the remaining burden, making this adequate but not complete.

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 coverage is 100%, so all four parameters including context, llm_model and conversation_id are fully documented in the schema. The description only restates that radioId is required, adding no meaning beyond it; baseline 3 applies.

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 concrete verb and resource: fetch roughly 25 tracks from a Deezer radio. The word 'radio' separates it from playlist/album/artist track listings among the siblings, though it never names those alternatives directly.

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 guidance is 'Requires `radioId`', which is a prerequisite rather than a when-to-use rule. It never says when to pick this over deezer_playlist_tracks_list or deezer_artist_top_tracks_list, nor what happens if the radio id is unknown beyond the schema note.

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