Skip to main content
Glama
qobuz-mcp
by cheubes

Add Tracks To Playlist

add_tracks_to_playlist

Append tracks in a specified order to the end of a Qobuz playlist you own by supplying the playlist ID and track IDs.

Instructions

Append tracks at the end of a playlist the user owns, in the given order.

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>",
      "track_ids": "<track_ids>"
    },
    "name": "add_tracks_to_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idsYesQobuz track IDs, in the order to add them.
playlist_idYesQobuz ID of a playlist the user owns.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the operation only works on user-owned playlists (an authorization requirement) and preserves insertion order. It says nothing about duplicate tracks, playlist size limits, or partial failure on invalid IDs, which are the main behavioral questions for an append operation.

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?

A single sentence with no filler, front-loading the action and resource before the ownership and ordering qualifiers. Nothing could be removed without losing meaning.

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 an output schema present, return values need no explanation, and annotations plus full schema coverage carry the safety and parameter burden. The only meaningful omission is duplicate/size-limit behavior, a minor gap for a low-complexity two-parameter 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 description coverage is 100%, so both parameters are already documented in the schema. The description's "in the given order" restates the ordering semantics already present in the track_ids schema description and adds no format or constraint detail beyond it, so the 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?

The description gives a specific verb and resource ("Append tracks") plus a location constraint ("at the end of a playlist"), which implicitly separates it from move_playlist_tracks and remove_tracks_from_playlist. It does not explicitly name or contrast a sibling tool, so it stops short of a 5.

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 phrase "a playlist the user owns" communicates a prerequisite, and "append at the end" implies the additive counterpart to removal/move tools. However, there is no explicit when-to-use/when-not guidance or named alternative, leaving the agent to infer the routing.

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