Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer related artists

deezer_artist_related_list
Read-onlyIdempotent

Retrieves up to 40 artists Deezer associates with a given artist ID, helping users discover similar music and expand their listening options.

Instructions

List up to 40 artists Deezer relates to an artist. Requires artistId. 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": {
      "artistId": "<artistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_artist_related_list"
  }
}

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`.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds the 40-item truncation limit and that the return is a list, which is genuine added context, but says nothing about ordering, pagination, availability of a 'next' cursor, or errors for invalid ids.

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, front-loaded with the capability and the 40-result cap, with zero filler. The middle sentence restates a requirement the schema already encodes, a minor waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotation explaining return shape, "Returns a list" is the only return information, leaving the agent unable to know what fields each artist entry contains or whether results are ordered or paginated. For a discovery tool whose whole value is the returned artist set, the definition is under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter already carries an inline description (artistId with an example and pattern, context, llm_model, conversation_id), so the schema does the heavy lifting. The description only repeats that artistId is required, which is redundant rather than additive; baseline is met but nothing extra is contributed.

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 and resource ("List ... artists Deezer relates to an artist") and pins the result cap at 40, which separates it from deezer_artist_get and deezer_artist_top_tracks_list by resource type. It does not explicitly name a sibling to distinguish against, 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?

Usage is only implied: the reader infers that this tool is for exploring an artist's sonic neighborhood, and "Requires `artistId`" is the only precondition stated. There is no when-to-use/when-not guidance and no routing to alternatives such as deezer_artist_get or deezer_artist_top_tracks_list.

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