Skip to main content
Glama
qobuz-mcp
by cheubes

Follow Playlist

follow_playlist

Add an editorial or another user's Qobuz playlist to your followed playlists by playlist ID, so it appears in your playlist list for quick access.

Instructions

Follow a playlist, such as an editorial or another user's playlist.

Followed playlists appear in list_my_playlists.

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": "follow_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 declare this is a non-destructive, open-world mutation (readOnlyHint=false, destructiveHint=false). The description adds real value beyond them by disclosing the observable side effect: the followed playlist shows up in list_my_playlists. It stops short of stating idempotency (what happens on a repeat follow) or auth requirements.

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 with zero waste; the core action is front-loaded and the second sentence delivers the consequential side effect.

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 well-documented parameter, an output schema, and annotations covering the safety profile, the definition covers everything essential. The only meaningful omission is repeat-follow behavior, a minor gap for this simple tool.

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?

Schema coverage is 100% and the single parameter is documented as a Qobuz playlist ID integer. The description adds only a light gloss on what kinds of playlists those IDs represent, which is marginal over the schema — baseline 3 applies.

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?

States a specific verb ("Follow") and resource ("playlist"), and clarifies the range of playlist types that can be followed (editorial or another user's). It is clearly distinct from unfollow_playlist, though it does not name the inverse explicitly.

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?

The description implies when to use it (to add a playlist to your library) and notes the result appears in list_my_playlists, but gives no explicit when-not guidance or prerequisites such as needing to know the playlist ID beforehand.

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