Skip to main content
Glama
qobuz-mcp
by cheubes

Update Playlist

update_playlist
Destructive

Changes a Qobuz playlist's name, description, visibility, or collaborative setting while preserving any fields not specified.

Instructions

Change a playlist's name, description, visibility or collaborative flag.

Only the fields given are changed; the others keep their current value.

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew name.
is_publicNoNew visibility.
descriptionNoNew description.
playlist_idYesQobuz ID of a playlist the user owns.
is_collaborativeNoWhether other users can edit it.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
nameYes
ownerYes
is_publicYes
updated_atYes
descriptionYes
tracks_countYes
duration_secondsYes
is_collaborativeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the write profile is known. The description adds genuinely useful PATCH-style semantics ('only the fields given are changed'), but it never explains what makes the operation destructive — e.g. that existing values are overwritten — nor mentions the ownership/permission requirement for mutating a playlist.

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 scope of mutable fields is front-loaded and the partial-update rule follows immediately. Nothing is repeated from the schema or annotations.

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 annotations and an output schema already supplied, the description only needs to cover field scope and update semantics, and it does both. It could go further by noting the ownership constraint and the overwrite behavior behind destructiveHint, but nothing essential for invoking the tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the sentence 'Only the fields given are changed; the others keep their current value' resolves a real ambiguity in the schema: all four editable params are nullable with default null, and the schema alone does not say whether null means 'clear the value' or 'leave unchanged'. That clarification adds meaning beyond the structured fields.

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 states a specific verb (change) and resource (playlist) and enumerates the exact mutable fields (name, description, visibility, collaborative flag), which implicitly separates it from siblings like add_tracks_to_playlist or delete_playlist. It stops short of naming any sibling explicitly, so differentiation is inferred from the field scope rather than stated.

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 only implied: an agent can infer this is the tool for metadata edits on an existing playlist, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as create_playlist for new playlists. The ownership prerequisite appears only in the schema, not the description.

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