Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Deezer artists

deezer_artists_batch_get
Read-onlyIdempotent

Retrieve up to 200 Deezer artists in a single request by ID, with any IDs that match nothing returned in the response list for easy validation.

Instructions

Get up to 200 Deezer artists 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_artists_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated Deezer artist 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 traits. The description adds genuinely new behavior beyond them: the per-request ceiling and, importantly, that unmatched ids are surfaced in the result rather than causing an error — a meaningful partial-failure contract.

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 batch scope and the cap, with nothing redundant beyond the near-trivial 'Returns a list'. Efficient, though that last sentence barely earns its place.

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 4-parameter read-only batch lookup with full schema coverage and rich annotations, the description supplies the limits, the missing-id behavior, and the return shape (no output schema exists). Only rate limits and error conditions are unaddressed, which are minor here.

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 schema already documents ids, context, llm_model, and conversation_id. The description's only parameter remark ('Requires `ids`') repeats what the required array already declares and adds no format or edge-case detail, so it lands at baseline.

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 concrete verb and resource with batch scope ('Get up to 200 Deezer artists in one request'), which implicitly separates it from the singular deezer_artist_get. It does not name a sibling or contrast explicitly, so it stops short of a 5.

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 'in one request' and 200-id cap imply this is the bulk path rather than the single-artist path, but the description never says when to prefer it over deezer_artist_get or what to do for more than 200 ids. Usage is inferable, not stated.

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