Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Deezer albums

deezer_albums_batch_get
Read-onlyIdempotent

Retrieve up to 200 Deezer albums in one request and identify album IDs that match nothing.

Instructions

Get up to 200 Deezer albums 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_albums_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated Deezer album 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

A3.5/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 the safety profile is covered. The description adds real behavioral value beyond that: the 200-id ceiling and the fact that non-matching ids are listed rather than causing an error. It does not describe ordering or the per-album result shape, which keeps it from a 5.

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 clauses, front-loaded with the most decision-relevant fact (batch size), with no filler or repetition of boilerplate. 'Returns a list' is near-zero information and could be dropped, but the rest is tight.

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 full schema coverage, rich annotations, and no output schema, the description covers the operationally important facts: batch limit and miss-handling. Remaining gaps (result ordering, partial-failure semantics beyond 'listed') are minor for a read-only batch fetch.

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 requiredness of `ids` and the 1-200 range are already documented in the schema. The description only restates 'Requires `ids`' and the cap, adding no format, encoding, or ordering semantics beyond what is already structured. Baseline 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 ('Get'), resource ('Deezer albums'), and batching scope ('up to 200 ... in one request'), which cleanly separates it from the singular deezer_album_get. It stops short of explicitly naming a sibling alternative, but the batch framing makes the distinction obvious.

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 phrase 'in one request' hints at batch efficiency but gives no explicit when-to-use guidance, no threshold for batching vs single lookups, and no mention of when to prefer deezer_album_get or deezer_artist_albums_list. An agent must infer the selection rule from tool names 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