Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Deezer playlists

deezer_playlists_batch_get
Read-onlyIdempotent

Fetch up to 200 public Deezer playlists by ID in a single request and identify IDs that return no matching playlist.

Instructions

Get up to 200 public Deezer playlists in one request; ids that match nothing are listed. Requires ids. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated Deezer playlist ids, 1 to 200.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and idempotence need no restating. The description does add two real facts — only public playlists are returned, and unmatched ids are listed — but "ids that match nothing are listed" is ambiguous about whether they appear in output or in a separate errors field, and no ordering or pagination behavior is given.

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 capability, the requirement, and the return shape front-loaded — no padding. "Requires `ids`" is slightly redundant given the required list and schema, costing a small amount of space.

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?

There is no output schema, so "Returns a list" is thin: it does not say whether results preserve request order, whether gaps are dropped or errored, or what a partial match looks like. For a batch getter where order and missing-id handling drive correct downstream use, this is an adequate but incomplete definition.

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%, with the ids array fully documented including the 1–200 bounds and the numeric pattern, so the schema carries the parameter burden. The description only restates "Requires `ids`" and adds no format, ordering, or duplicate-id semantics beyond the schema.

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 states a specific verb and resource ("Get ... Deezer playlists") and adds batch scope ("up to 200 ... in one request"), which implicitly separates it from the single-playlist sibling. It does not name deezer_playlist_get explicitly, so the differentiation is inferential rather than stated.

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 phrase "in one request" implies the batch use case versus repeated single fetches, but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative. The agent can infer the intent but must supply its own routing logic.

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