Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer artist top tracks

deezer_artist_top_tracks_list
Read-onlyIdempotent

Fetch a Deezer artist's most played tracks using an artist ID and return up to 100 results for music discovery or playlist research.

Instructions

List a Deezer artist's most played tracks, up to 100. 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_top_tracks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 100. Default: 50.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered without the description. The description adds only the 100-item cap and that a list is returned; it says nothing about pagination, ordering guarantees, or the context/conversation_id protocol the schema imposes.

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 purpose and free of filler. 'Returns a list' is largely redundant given the tool name and slightly wastes space, but nothing is buried or padded.

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

Completeness3/5

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

With no output schema, the description carries some burden for describing return values, and 'Returns a list' is minimal but directionally sufficient for a simple read tool. It leaves the response shape (track fields, paging via limit) and the multi-call conversation_id handshake unaddressed, which is a gap for a five-parameter tool.

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 limit (1-100, default 50), artistId format and the context/llm_model/conversation_id parameters. The description only restates that artistId is required and that the cap is 100, both already in the schema, so 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 gives a specific verb and resource ('List a Deezer artist's most played tracks') plus a scope cap ('up to 100'), which is enough to distinguish it from retrieval tools like deezer_artist_get. It does not, however, explicitly distinguish itself from close siblings such as deezer_artist_mix_list or deezer_playlist_tracks_list.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The only selection aid is the implicit condition 'you have an artistId', leaving the agent to infer why it should pick this over the other artist-list tools.

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