Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer artist

deezer_artist_get
Read-onlyIdempotent

Fetch a Deezer artist by ID to get fan counts, biography, links, banner, names in other scripts, and featured playlists.

Instructions

Get a Deezer artist with fans, biography, links, banner, names in other scripts and featured playlists. Requires artistId.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
artistIdYesRequired. Deezer artist id, for example `27`.
languageNoTwo-letter language code for editorial text, such as `fr`. Titles and names are not translated. Default: `en`.
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 value by enumerating exactly what the response contains (fan counts, biography, links, banner, localized names, featured playlists), which matters because there is no output schema. It does not discuss rate limits or error behavior, keeping it short of 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?

Two compact sentences with the payload description front-loaded. The trailing "Requires `artistId`" is largely redundant with the schema's required list, which is the only real waste.

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 lookup with no output schema, the description supplies the return-field summary an agent needs to decide whether this tool answers the question. The three non-obvious infrastructure parameters (context, llm_model, conversation_id) are left entirely to the schema, which documents them well, so this is close to complete.

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 artistId, language, context, llm_model and conversation_id are all documented in the schema itself. The description only echoes that artistId is required and adds no format or fallback detail, so the baseline of 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 uses a specific verb and resource ("Get a Deezer artist") and enumerates the payload contents (fans, biography, links, banner, alternate-script names, featured playlists). This clearly separates it from the sibling list tools like deezer_artist_albums_list or deezer_artist_top_tracks_list, though it does not name any alternative explicitly.

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 only usage statement is "Requires `artistId`", which restates the schema's required field rather than explaining when to choose this tool. There is no mention of when to use deezer_artists_batch_get for multiple artists or the appleMusic/spotify equivalents for other services, and no exclusions or preconditions beyond the id requirement.

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