Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer account playlists

deezer_user_playlists_list
Read-onlyIdempotent

Retrieve a Deezer account's public playlists by user ID, with pagination support for browsing large collections.

Instructions

List a Deezer account's public playlists. Requires userId. 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": {
      "userId": "<userId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_user_playlists_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.
userIdYesRequired. Deezer account id, for example `753546365`.
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

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 real value by disclosing that only public playlists are returned and that pagination uses a cursor, but it says nothing about authentication scope or what happens when the account has no public 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?

Three short sentences with the core purpose front-loaded and zero filler. The second and third sentences partly duplicate schema declarations, 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 filtered-list tool with full schema coverage and rich annotations, the description covers scope, the required parameter, and pagination. It still lacks return-shape detail (no output schema exists) and any routing guidance among the many sibling list tools, leaving modest gaps.

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 userId, cursor, limit, context, llm_model, and conversation_id is already documented in the schema. The description's mentions of userId and cursor merely restate schema content without adding format or edge-case meaning, 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?

States a specific verb and resource ('List a Deezer account's public playlists') and narrows the scope with 'public', which meaningfully separates it from an artist-playlist or library listing. It does not explicitly name a sibling such as deezer_artist_playlists_list, so an agent must infer the distinction from the word 'account'.

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 offered is the prerequisite 'Requires `userId`' and a parenthetical note about cursors when paginated. There is no statement of when to prefer this over sibling tools like deezer_artist_playlists_list, deezer_user_library_list, or deezer_playlists_batch_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