Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer show

deezer_show_get
Read-onlyIdempotent

Fetch a Deezer podcast show by show ID to view its publisher, description, episode count, and availability.

Instructions

Get a Deezer podcast show with its publisher, description, episode count and availability. Requires showId.

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

Input Schema

NameRequiredDescriptionDefault
showIdYesRequired. Deezer podcast show id, for example `1000702442`.
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.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds real value by naming the fields returned (publisher, description, episode count, availability), telling the agent what data to expect without a separate output schema. It omits behavior on invalid or missing show IDs and any effect of the language parameter on the returned description.

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 with the retrieved content front-loaded and no filler. The second sentence largely restates the schema's required-field list, which is minor redundancy rather than bloat.

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 single-record read tool with no output schema, describing the returned fields is the key missing piece and the description supplies it. Remaining gaps (invalid-ID behavior, how language affects editorial text) are small and partly covered by the schema's parameter descriptions.

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 including showId, context, language, llm_model and conversation_id is documented inline with examples. The description adds nothing beyond repeating the showId requirement, so the 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 show') and enumerates what the result contains (publisher, description, episode count, availability), which distinguishes it from sibling list tools like deezer_show_episodes_list. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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 the prerequisite 'Requires `showId`.' There is no statement of when to prefer this over deezer_show_episodes_list or deezer_episode_get, and no exclusions or error conditions. An agent must infer the use case from the purpose sentence alone.

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