Remove a Deezer playlist from your account by providing its playlist ID. Deletes the playlist permanently to clean up your music library.
Delete a playlist.
| Name | Required | Description | Default |
|---|---|---|---|
| playlist_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only states action without disclosing permanence, side effects, or authorization needs. Minimal transparency.
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?
Extremely concise to the point of underspecification. A single phrase lacks front-loading of critical details; could expand without losing efficiency.
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?
Simple tool but missing return value description, error handling, or idempotency details. Incomplete given lack of output schema and parameter documentation.
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 0%, and description does not clarify the parameter 'playlist_id' (e.g., format, source, validation). Agent cannot infer how to obtain or format this value.
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?
Description clearly states 'Delete a playlist' with a specific verb and resource. It distinguishes from siblings like remove_tracks_from_playlist, though it could be more precise about scope (e.g., permanent deletion).
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 like remove_tracks_from_playlist or update_playlist. Missing context about prerequisites or caveats.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.