Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer genre artists

deezer_genre_artists_list
Read-onlyIdempotent

Use a Deezer genre ID to list up to 50 artists featured in that genre, enabling genre-based artist discovery.

Instructions

List the artists Deezer features in a genre, up to 50. Requires genreId. 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": {
      "genreId": "<genreId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_genre_artists_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
genreIdYesRequired. Genre id from the genres list, or `0` for 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds two useful facts beyond that: the 50-item cap and the fact that a list is returned. It says nothing about ordering, filters, or pagination, which keeps it at a moderate score.

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 with the core scope front-loaded and no filler. The final "Returns a list" is slightly redundant but does convey return shape, so it largely earns its place.

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 simple read-only list endpoint with full schema coverage and no output schema, the definition covers scope, requirement, and result size. Only the lack of guidance on sourcing genreId from the genres list is a meaningful omission.

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 (genreId, context, llm_model, conversation_id) is already documented in the schema. The description merely reiterates that genreId is required and adds no new meaning, which is the baseline expectation when the schema does the heavy lifting.

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 states a specific verb and resource ("List the artists ... in a genre") and includes the cap of 50, so the agent knows exactly what the tool returns. It stops short of naming a differentiating sibling, but the resource scope is unambiguous against siblings like deezer_genres_list or deezer_artist_albums_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 explicit when-to-use guidance, no exclusions, and no pointer to deezer_genres_list for obtaining the required genreId. The only prerequisite signal ("Requires genreId") duplicates the schema rather than orienting the agent.

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