Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Deezer tracks

deezer_tracks_batch_get
Read-onlyIdempotent

Fetch up to 200 Deezer tracks in one request using their IDs; unmatched IDs are returned in the response so you can identify missing tracks.

Instructions

Get up to 200 Deezer tracks 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_tracks_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated Deezer track 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.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the bar is low. The description still adds genuinely useful context beyond them: the partial-failure behavior ('ids that match nothing are listed') and the fact that the return is a list. It does not mention ordering or what fields each track carries, which would be the remaining gap.

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 tight clauses with the load-bearing detail (batch size, unmatched ids, required input) front-loaded and no filler sentences. 'Returns a list' is slightly obvious but does confirm the output shape in the absence of an output 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?

For a simple batch lookup with no output schema, the description covers what it does, the size ceiling, required input, partial-failure handling, and return shape. What remains unsaid, such as per-item fields and ordering, is minor for a read-only getter.

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%, including the 1-200 id constraint, so the schema carries the parameter meaning. The description's 'Requires `ids`' and the 200 cap merely restate the schema, and the meta parameters (context, llm_model, conversation_id) are not discussed at all. 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?

The description names a specific verb and resource (get Deezer tracks) and states the batch scope explicitly: 'up to 200 ... in one request.' That scope, plus the id-based lookup, tells an agent this is the bulk-fetch tool rather than the single-track or ISRC lookups, though it never names those alternatives directly.

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?

Usage is only implied: gathering many ids into one request is the obvious trigger. There is no explicit when-to-use or when-not guidance, and no routing to siblings such as deezer_track_by_isrc_get or the album/playlist track list tools, so an agent must infer the boundary.

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