Skip to main content
Glama
qobuz-mcp
by cheubes

Move Playlist Tracks

move_playlist_tracks
Destructive

Reorder tracks in a Qobuz playlist by moving specified playlist track IDs in front of a chosen 1-based position; use 0 to move them first or tracks_count + 1 to move them last.

Instructions

Reorder entries within a playlist the user owns.

The entries, identified by playlist_track_id, are moved in front of the entry currently at position insert_before (positions as returned by get_playlist, starting at 1).

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>",
      "playlist_track_ids": "<playlist_track_ids>",
      "insert_before": "<insert_before>"
    },
    "name": "move_playlist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYesQobuz ID of a playlist the user owns.
insert_beforeYes1-based position of the entry to move them in front of; 0 moves them first, `tracks_count + 1` moves them last.
playlist_track_idsYes`playlist_track_id` values from `get_playlist`, not track IDs.

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

A4/5.0
Behavior4/5

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the description's real contribution is the precise move semantics: entries are relocated to sit in front of a given position, with positions anchored to get_playlist output. That resolves the main ambiguity of a reorder operation, though it says nothing about failure modes for invalid positions or whether the move is atomic.

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, front-loaded with the operation and followed by the one non-obvious mechanic. Nothing is padding.

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 and all three parameters fully described, the description covers what an agent needs to construct a correct call. Only edge-case behavior (out-of-range insert_before, empty results) is left implicit.

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 schema already explains insert_before sentinel values (0 first, tracks_count+1 last) and that playlist_track_ids are track IDs from get_playlist, not catalog track IDs. The description repeats the 1-based position framing rather than adding new meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Reorder entries within a playlist the user owns" gives a specific verb (reorder) and resource (playlist entries), which cleanly separates it from add_tracks_to_playlist, remove_tracks_from_playlist and update_playlist without ambiguity.

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 usage (changing entry order within an existing owned playlist) and states the ownership precondition, but it never explicitly says when to pick this over update_playlist or the add/remove tools, nor when not to use it.

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