Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer show episodes

deezer_show_episodes_list
Read-onlyIdempotent

List a Deezer podcast show's episodes newest first, with paging via cursor. Use showId to retrieve and paginate episodes for browsing or research.

Instructions

List the episodes of a Deezer podcast show, newest first, with paging. Requires showId. Returns a list (use cursor when paginated).

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_episodes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 100. Default: 50.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same.
showIdYesRequired. Deezer podcast show id, for example `1000702442`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: the result order (newest first) and that the response is a paginated list driven by a cursor.

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 compact sentences with the resource and ordering front-loaded. The parenthetical cursor remark is slightly redundant with the schema, but nothing is padded or buried.

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 filtered, paginated list tool with no output schema, the description covers resource, scope, ordering, return shape, and pagination mechanism. The three meta-parameters (context, llm_model, conversation_id) are fully described in the schema, so no gap remains for the agent.

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 every parameter including showId, limit, and cursor is already documented in the schema. The description only restates the showId requirement and the cursor mechanism, adding nothing beyond the ordering hint; baseline 3 applies when the schema does the heavy lifting.

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 ('List the episodes of a Deezer podcast show') with ordering ('newest first') and scoping ('Requires showId'). An agent can distinguish it from deezer_show_get or deezer_episode_get, though no sibling is named 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?

The prerequisite ('Requires showId') and the paging hint ('use cursor when paginated') give implied usage, but there is no explicit statement of when to choose this over deezer_show_get or deezer_episode_get, and no exclusions.

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