searchSearch Deezer for tracks/albums/artists/playlists.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | track | album | artist | playlist (default track) | |
| limit | No | 1-100 (default 25) | |
| query | Yes | e.g. "Daft Punk Get Lucky" |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Array of search results (tracks, albums, artists, or playlists) | |
| next | No | URL to next page of results | |
| total | No | Total number of results |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "query": "Daft Punk Get Lucky"
+ },
+ {
+ "limit": 10,
+ "query": "The Beatles",
+ "type": "artist"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Array of search results (tracks, albums, artists, or playlists)",
+ "items": {
+ "properties": {
+ "album": {
+ "description": "Album info for tracks",
+ "type": "object"
+ },
+ "artist": {
+ "description": "Artist info for tracks",
+ "type": "object"
+ },
+ "duration": {
+ "description": "Duration in seconds (for tracks)",
+ "type": "number"
+ },
+ "id": {
+ "description": "Resource ID",
+ "type": "number"
+ },
+ "name": {
+ "description": "Resource name (for artists/playlists)",
+ "type": "string"
+ },
+ "picture": {
+ "description": "Image URL",
+ "type": "string"
+ },
+ "preview": {
+ "description": "Preview URL",
+ "type": "string"
+ },
+ "title": {
+ "description": "Resource title or name",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "next": {
+ "description": "URL to next page of results",
+ "type": "string"
+ },
+ "total": {
+ "description": "Total number of results",
+ "type": "number"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the description adds little behavioral context. It does not contradict 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 a single concise sentence with no wasted words. It could be slightly more informative but is 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 presence of an output schema and simple functionality, the description is adequate. However, it lacks context on pagination or case sensitivity.
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 coverage is 100% with detailed parameter descriptions. The description does not add meaning beyond listing content types, so baseline score is appropriate.
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 clearly states it searches Deezer for tracks/albums/artists/playlists, specifying the resource and action. However, it does not differentiate from sibling tools like search_within or deep_research.
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?
No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites or exclusions, leaving the agent to infer usage.
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.