Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer genres

deezer_genres_list
Read-onlyIdempotent

Retrieve a complete list of Deezer music genres localized to a specified two-letter language code, so you can browse or categorize music by genre.

Instructions

List every Deezer genre, named in the language you ask for. Optional inputs: language. 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_genres_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered without prose. The description adds only that the result is a complete list (no pagination implied), but its claim that genres are 'named in the language you ask for' sits awkwardly against the schema note that names are not translated, creating ambiguity about what localization actually affects.

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 core action, with no filler. 'Returns a list' is nearly redundant with 'List every' and the only sentence that does not clearly earn its place.

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 simple read-only list endpoint with rich annotations and full schema coverage, the description covers the essentials and notes the return shape. It omits whether the list is paginated and what a genre entry contains, both of which would help an agent plan follow-up calls to deezer_genre_artists_list.

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 explains `language`, its pattern, and the default, as well as the boilerplate context/llm_model/conversation_id parameters. The description restates only `language` and adds no meaning beyond the schema — its phrasing about names being language-dependent is the one addition, and it muddies rather than clarifies.

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 every Deezer genre') and the word 'every' signals an unfiltered, complete catalog, which implicitly separates it from the *_list siblings that paginate an artist's or genre's contents. It does not explicitly name a sibling to contrast with, so it falls just short of full differentiation.

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: an agent can infer this is the catalog lookup to run before calling deezer_genre_artists_list, but the description never says when to prefer it or what alternative exists. No exclusions, prerequisites, or ordering guidance are stated.

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