Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer artist playlists

deezer_artist_playlists_list
Read-onlyIdempotent

List playlists that feature a Deezer artist by providing the artist ID. Supports pagination with a cursor to retrieve up to 100 playlists.

Instructions

List the playlists that feature a Deezer artist, up to 100. Requires artistId. 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": {
      "artistId": "<artistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_artist_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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
artistIdYesRequired. Deezer artist id, for example `27`.
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.6/5.0
Behavior3/5

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

Annotations already declare the tool read-only, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds the pagination behavior and result shape ('Returns a list'), but the 'up to 100' cap and cursor mechanics duplicate what the schema and annotations already convey. It does not disclose anything about result ordering or what fields each playlist carries.

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?

Three short sentences with the resource, the constraint, and the return shape front-loaded. Nothing is wasted and there is no filler.

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 simple read-only list tool with a fully documented schema and clear annotations, the description covers purpose, prerequisite, and pagination adequately. Only the lack of routing to a sibling keeps it from being complete.

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 context, llm_model, and conversation_id is documented in the schema. The description only restates that `artistId` is required and echoes the cursor guidance, adding no new meaning. Baseline 3 is appropriate.

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 playlists that feature a Deezer artist') and bounds the scope ('up to 100'). The word 'artist' implicitly separates it from deezer_user_playlists_list, but no sibling is named explicitly, so it stops short of full differentiation.

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?

It gives the prerequisite ('Requires `artistId`') and a pagination cue ('use cursor when paginated'), which is useful context. It never says when to prefer this over deezer_user_playlists_list, deezer_artist_mix_list, or deezer_playlists_batch_get, so usage is only implied.

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