chartCurrent chart (top tracks/albums/artists). Pass genre_id 0 for worldwide.
| Name | Required | Description | Default |
|---|---|---|---|
| genre_id | No | Default 0 (all genres). |
| Name | Required | Description | Default |
|---|---|---|---|
| albums | No | ||
| tracks | No | ||
| artists | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "genre_id": 0
+ },
+ {
+ "genre_id": 132
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "albums": {
+ "properties": {
+ "data": {
+ "description": "Top chart albums",
+ "items": {
+ "properties": {
+ "cover": {
+ "description": "Album cover URL",
+ "type": "string"
+ },
+ "id": {
+ "description": "Album ID",
+ "type": "number"
+ },
+ "title": {
+ "description": "Album title",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "artists": {
+ "properties": {
+ "data": {
+ "description": "Top chart artists",
+ "items": {
+ "properties": {
+ "id": {
+ "description": "Artist ID",
+ "type": "number"
+ },
+ "name": {
+ "description": "Artist name",
+ "type": "string"
+ },
+ "picture": {
+ "description": "Artist image URL",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "tracks": {
+ "properties": {
+ "data": {
+ "description": "Top chart tracks",
+ "items": {
+ "properties": {
+ "duration": {
+ "description": "Duration in seconds",
+ "type": "number"
+ },
+ "id": {
+ "description": "Track ID",
+ "type": "number"
+ },
+ "preview": {
+ "description": "Preview URL",
+ "type": "string"
+ },
+ "title": {
+ "description": "Track title",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and not destructive. The description adds 'Current chart' implying recent data, but doesn't go beyond annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no superfluous words, front-loaded with key purpose. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, annotations cover safety, and output schema exists, the description adequately covers purpose and parameter usage. Missing details about genre_id range or return format, but output schema presumably handles that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 100% coverage with description 'Default 0 (all genres).' The description adds context that 0 means worldwide, which is helpful but only marginally extends the schema's information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it returns the current chart of top tracks/albums/artists, distinguishing from siblings like album, artist, track which focus on individual entities. However, it doesn't specify whether all three categories are returned in one chart or separately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a usage hint ('Pass genre_id 0 for worldwide') but does not explicitly state when to use this tool versus alternatives like artist or track tools. No guidance on when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools overlap in purpose (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research all route queries to structured data), and the set mixes Deezer music tools with an unrelated Pipeworx/Polymarket suite. An agent would struggle to pick the right tool for a given request.
Naming is mixed: single-word nouns (album, artist, track, chart), verb_noun snake_case (list_subscriptions, resolve_entity), and verbose multi-concept names (scan_competitor_ai_presence, polymarket_kalshi_spread). No consistent pattern across the set.
37 tools for a server named 'Deezer' is far beyond a music API scope; the overwhelming majority are unrelated data-research, prediction-market, and utility tools. This is an extreme mismatch between the server name and the tool surface.
For the Deezer music domain, the surface is incomplete (no playlists, user library, lyrics, or radio), while the many unrelated tools each cover only fragments of their domains. The overall set lacks coherent coverage of any single purpose.