Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer account favourites

deezer_user_library_list
Read-onlyIdempotent

List a Deezer account's favorite albums, artists, or tracks by user ID and library type, returning paginated results for browsing or exporting a music library.

Instructions

List a Deezer account's favourite albums, artists or tracks. Requires userId and kind. 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>",
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_user_library_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesRequired. Which part of the library to list.
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

A3.6/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 fully covered without the description. The description adds a pagination cue ('use cursor when paginated'), but that behavior is also spelled out in the `cursor` schema field, so the added value is modest rather than substantive.

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 short sentences, front-loaded with the action and resource, with the requirement and return-shape notes following. Nothing is redundant or padded.

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 read-only paginated list tool with 100% schema coverage and full annotations, the description covers purpose, required inputs and return shape ('Returns a list'). The only gap is that, with no output schema, it does not hint at what fields each returned item carries, but that is a minor omission given the tool's simplicity.

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 all seven parameters including `kind`'s enum and `cursor`'s usage are already documented in structured form. The description only echoes that `userId` and `kind` are required, adding no new meaning such as default page size or expected id format.

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 favourite albums, artists or tracks' — which cleanly separates it from sibling playlist/artist listing tools by the 'favourite library' scope. It stops short of explicitly naming a sibling alternative, so it is clear but not maximally differentiating.

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 only usage signal is the requirement statement ('Requires `userId` and `kind`'), which is really parameter restatement rather than when-to-use guidance. There is no statement about when to prefer this over `deezer_user_playlists_list` or `deezer_user_get`, leaving the routing decision implied by the word 'favourite' alone.

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