Skip to main content
Glama
qobuz-mcp
by cheubes

Unfollow Playlist

unfollow_playlist
Destructive

Stop following a Qobuz playlist without deleting it. Use the playlist ID to remove it from your followed playlists while leaving the playlist itself intact.

Instructions

Stop following a playlist. The playlist itself is not deleted.

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": "unfollow_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYesQobuz playlist ID (an integer).

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is carried structurally. The description adds genuinely useful context that those hints cannot: the destructive effect is limited to the follow relationship, not the playlist resource itself, which prevents an agent from avoiding this tool out of fear of data loss. It does not address idempotency or what happens when the playlist is not followed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the action first and the non-destructive clarification second. Nothing is superfluous and the key reassurance is front-loaded rather than buried.

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

Completeness4/5

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

With a single fully documented parameter, an output schema, and annotations covering the safety profile, the definition covers what an agent needs to invoke it. The only remaining gap is edge-case behavior such as calling it on a playlist that is not followed, which is minor for a tool of this simplicity.

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

Parameters3/5

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

There is a single required parameter with 100% schema description coverage ('Qobuz playlist ID (an integer)'), so the schema already does the explanatory work. The description adds no meaning beyond it, which is the expected baseline for a one-parameter tool at full coverage.

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 gives a specific verb and resource ('Stop following a playlist') rather than restating the title, and the second sentence implicitly separates it from delete_playlist by stating the playlist survives. It stops short of naming any sibling explicitly, so an agent still has to infer that this is the library-membership counterpart to follow_playlist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the action itself: an agent can reasonably read this as 'use when you want to remove a playlist from the user's library without deleting it.' There is no explicit statement of when to prefer this over delete_playlist or remove_tracks_from_playlist, and no mention of preconditions such as the playlist needing to be followed already.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.