Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer editorial page

deezer_pages_get
Read-onlyIdempotent

Fetches a Deezer editorial page such as home, charts, moods, genres, radios, podcasts, or a channel and returns its sections of items. Specify a path and language to target the content.

Instructions

Get one of Deezer's editorial pages (home, charts, moods, genres, radios, podcasts or a channel) as sections of items. Optional inputs: path and language.

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_pages_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoWhich page: `home`, `channels/explore`, `channels/charts`, `channels/moods`, `channels/genres`, `channels/radios`, `channels/podcasts`, any `channels/{slug}` or a section's `moreTarget`. Default: `home`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.2/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 covered. The description contributes the return structure ('sections of items') and confirms editorial scope, but says nothing about language fallback behavior, whether pages are cached/curated by region, or how much content a 'section' contains. Given annotation coverage, this is adequate but not rich.

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 short sentences, front-loaded with the verb and resource, with the optional inputs listed last. Slight redundancy in re-listing page categories that the path schema already enumerates, but no filler or repetition of annotation facts.

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?

For a read-only lookup with full schema coverage and clear annotations, most of what an agent needs is present. However, with no output schema, the description carries the burden of explaining returns and does so only with the vague phrase 'sections of items' — leaving the item shape, section count, and language-affected fields unexplained.

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 both path and language are already fully documented, including the allowed page values and the two-letter-code rule. The description only repeats that these are optional inputs and adds no format, default, or interaction detail beyond the schema; baseline 3 applies. The two required parameters (context, llm_model) are not mentioned but are self-documented in the schema.

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 names a specific verb (get) and resource (Deezer editorial pages) and enumerates the page families (home, charts, moods, genres, radios, podcasts, channel). It also states the return shape ('sections of items'), so an agent knows what it receives. It stops short of distinguishing itself from Deezer siblings such as deezer_charts_get or deezer_station_get, which overlap on charts/radio content.

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: nothing says to prefer this over deezer_charts_get for chart data or over deezer_station_get for radio content. The only routing hint is the enumeration of page types, which merely implies the domains this tool covers rather than stating selection criteria.

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