Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer playlist

deezer_playlist_get
Read-onlyIdempotent

Retrieve a Deezer playlist's details by playlist ID, including track and editorial info, so you can inspect or reuse playlist data in your workflow.

Instructions

Get a Deezer playlist's details. Requires playlistId.

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

Input Schema

NameRequiredDescriptionDefault
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.
playlistIdYesRequired. Deezer playlist id, for example `908622995`.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The only added statement, "Requires playlistId", restates the schema and contributes no new behavioral context such as error handling for unknown ids or what happens on private playlists.

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 action, with no filler. The second sentence is largely redundant against the schema's "Required. Deezer playlist id" description, which slightly weakens the otherwise tight structure.

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?

This is a simple read tool with rich annotations, full schema coverage and no output schema, so the description need not explain return values. However, "details" is unspecified and no error or edge-case behavior is mentioned, leaving it only minimally adequate for the tool's complexity.

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%, so every parameter including playlistId, language, context, llm_model and conversation_id is already documented in the schema. The description adds no syntax, format or default information beyond what the schema provides, so the baseline of 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?

The description names a specific verb and resource ("Get a Deezer playlist's details"), so the agent knows this returns a single playlist's metadata. It does not distinguish itself from close siblings such as deezer_playlist_tracks_list or deezer_playlists_batch_get, leaving the single-vs-collection boundary implicit.

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 beyond the schema-level requirement of playlistId. The description does not say when to prefer this over the tracks listing or the batch variant, nor does it mention any preconditions such as the conversation_id handshake described in the schema.

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