Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer episode

deezer_episode_get
Read-onlyIdempotent

Retrieve a Deezer podcast episode by episode ID and receive the publisher's original audio link for playback or download.

Instructions

Get a Deezer podcast episode with the publisher's own audio link. Requires episodeId.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
episodeIdYesRequired. Deezer podcast episode id, for example `871770701`.
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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the response includes the publisher's own audio link — but says nothing about error behavior for invalid ids, whether the id is global across shows, or response shape.

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?

Two short sentences, front-loaded with the purpose, with no filler prose. The second sentence is partly redundant with the schema's required list, which keeps it just short of a 5.

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 a simple read-only getter with full schema coverage and complete annotations, the definition is minimally sufficient: an agent can call it correctly. It still leaves gaps around how this differs from deezer_show_get and what the returned episode payload includes beyond the audio link.

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%, including a pattern and a concrete example (`871770701`) for episodeId, so the schema does the heavy lifting. The description only repeats that episodeId is required and adds no format, range, or id-origin semantics; 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 specific verb and resource ('Get a Deezer podcast episode') and adds a distinguishing detail: the result carries the publisher's own audio link, which separates it from a generic show lookup. It does not, however, distinguish itself from siblings like deezer_show_get or dev_to_podcast_episode_get, so an agent must still infer the boundary.

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?

There is no when-to-use guidance, no when-not-to-use condition, and no named alternative. The only usage statement, 'Requires episodeId,' restates the schema's required field rather than telling the agent under what circumstances this tool is the right choice over the other episode/show tools.

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