artist_topDeezer music catalogue — the most-streamed tracks for one Deezer artist id, up to 100. Each track returns its Deezer track id, title, rank, duration, album and a 30-second preview URL. Answers what an artist's biggest songs are on Deezer.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| limit | No | 1-100 (default 25) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Array of top tracks by the artist |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "id": 27
+ },
+ {
+ "id": 27,
+ "limit": 10
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Array of top tracks by the artist",
+ "items": {
+ "properties": {
+ "album": {
+ "description": "Album info",
+ "type": "object"
+ },
+ "artist": {
+ "description": "Artist info",
+ "type": "object"
+ },
+ "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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds behavioral context by detailing the output fields (track id, title, rank, duration, album, 30-second preview URL) and the limit of up to 100 tracks, which is useful beyond the annotations.
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?
The description is three concise sentences with no irrelevant content. The first sentence states the core function, the second details the output fields, and the third reinforces the purpose. Every sentence earns its place.
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 has an output schema and annotations covering safety, the description provides sufficient context: it identifies the input (artist id, optional limit), the output fields, and the intended use case. It is complete for a simple read-only lookup tool.
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?
The input schema describes only the limit parameter (1-100, default 25), not the id. The description clarifies that id is a Deezer artist id and that results are limited to up to 100, partially compensating for the missing id description. This adds meaning beyond the schema.
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?
The description uses a specific verb ('returns') and clearly identifies the resource: 'the most-streamed tracks for one Deezer artist id, up to 100.' It also explicitly states the purpose: 'Answers what an artist's biggest songs are on Deezer.' This distinguishes it from sibling tools like artist or track.
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?
The description provides a clear usage context by stating the tool answers what an artist's biggest songs are, implying it should be used for artist top tracks. However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of full guidance.
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.