Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer playlist tracks

deezer_playlist_tracks_list
Read-onlyIdempotent

Lists tracks in a Deezer playlist in order with each track's date added. Use the playlist ID and paginate with a cursor for up to 1,000 tracks per page.

Instructions

List a Deezer playlist's tracks in order with the date each was added, up to 1,000 per page. Requires playlistId. 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": {
      "playlistId": "<playlistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_playlist_tracks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 1000. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same.
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.
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered by structured data. The description still adds real value by disclosing the page cap of 1,000, result ordering, and the presence of an added-date field plus cursor pagination — traits not visible in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the core behavior and constraints front-loaded; no filler, and the required-parameter note is placed where an agent will see it before scanning the schema.

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?

With no output schema, the description does carry the return-value burden, and it does state the result is an ordered track list with added dates and that pagination uses a cursor. It stops short of describing item fields or what an empty/deleted playlist returns, but the essentials for correct invocation are present.

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 the schema already documents every parameter including `limit`, `cursor` and `playlistId`. The description only restates that `playlistId` is required and echoes the cursor rule, adding no format, range, or syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 playlist's tracks'), plus scope details (in order, date added, 1,000 per page) that separate it from the sibling `deezer_playlist_get` (playlist metadata) and the various artist/radio track listers.

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?

Says the tool requires `playlistId` and that the cursor should be used once paginated, which gives some operational context. However, it never states when to pick this over alternatives such as `deezer_tracks_batch_get` or a playlist metadata call, and there are no explicit 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