Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer chart

deezer_charts_get
Read-onlyIdempotent

Fetch Deezer chart data for tracks, albums, artists, playlists, or podcasts by type, genre, country, and limit to retrieve ranked lists for music research.

Instructions

Get a Deezer chart of tracks, albums, artists, playlists or podcasts, with a country for the tracks chart. Optional inputs: type, genreId, country and limit. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_charts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhich chart. Default: `tracks`.
limitNoItems per page, 1 to 300. Default: 100.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter country code for the tracks chart, for example `BR`. Only with `type=tracks` and all genres; the other charts follow Deezer's default region.
genreIdNoGenre id from the genres list; `0` (default) is all genres.
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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is fully covered structurally. The description adds only the return-shape hint ('Returns a list') and the country/tracks scoping note; it says nothing about pagination behavior, rate limits, or whether results vary by region beyond what the schema states.

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 sentences, front-loaded with the action and resource, with no filler. The listing of optional inputs is mild redundancy against the schema but reasonable for quick scanning.

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 list tool with no output schema, the description states the return is a list and the schema fully documents all seven parameters, including the unusual context/llm_model/conversation_id plumbing. An agent has enough to call it correctly; only pagination/response detail is absent.

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 every parameter is already documented, including the country constraint for type=tracks and genreId=0 meaning all genres. The description merely restates the parameter names without adding format or edge-case detail, so the 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 (get a Deezer chart) and enumerates the chart types (tracks, albums, artists, playlists, podcasts), which tells the agent exactly what this returns. It does not differentiate itself from sibling list tools like deezer_artist_top_tracks_list or deezer_genres_list, 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 description names the optional inputs and notes that a country applies 'for the tracks chart', which implies when those inputs matter. However, there is no explicit when-to-use vs. when-not guidance or comparison to alternatives such as the per-artist top-tracks list, leaving selection largely to inference.

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