Skip to main content
Glama
Sign In
mcp-deezer

mcp-deezer

by Benitoow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_playlist

Retrieve Deezer playlist details and tracks by playlist ID, with an optional limit on the number of tracks returned.

Instructions

Get playlist details with tracks.

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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYes
tracks_firstNoMax tracks (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description bears full responsibility. It only states the action without disclosing side effects, pagination, auth requirements, or performance implications. It does not contradict annotations but is insufficient.

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?

The description is very short and front-loaded. It is concise but not overly verbose. However, it could benefit from slightly more detail without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and two parameters, the description is too minimal. It omits details about returned fields, track pagination, and ordering, making it incomplete for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, with only tracks_first described. The tool description adds no extra meaning to the parameters; it does not clarify what playlist_id should be or how tracks_first affects results.

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 clearly states it gets playlist details with tracks, using a specific verb and resource. It distinguishes from sibling tools like get_album or get_track, though it could be more precise about what details are included.

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?

No guidance on when to use this tool versus alternatives like get_user_playlists or get_favorite_playlists. The context of use is implied but not explicitly 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