Skip to main content
Glama
qobuz-mcp
by cheubes

Remove Tracks From Playlist

remove_tracks_from_playlist
Destructive

Removes specific entries from a Qobuz playlist you own by playlist_track_id, deleting only the targeted track occurrence when duplicates exist.

Instructions

Remove entries from a playlist the user owns.

Entries are identified by playlist_track_id, so only the targeted occurrence of a track that appears several times is removed.

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

Input Schema

NameRequiredDescriptionDefault
playlist_idYesQobuz ID of a playlist the user owns.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by explaining that only the targeted occurrence of a duplicated track is removed, which is exactly the ambiguity an agent would otherwise have. It stops short of stating irreversibility or partial-failure behavior on a batch.

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 sentences with no filler, and the ownership constraint plus the identifier caveat are front-loaded before the schema is even consulted. Nothing is repeated or padded.

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?

An output schema exists, so return values need not be described, and the two required parameters are fully covered by the schema. The remaining gap is behavioral: it does not say whether a batch removal is atomic or whether the operation is reversible.

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 says playlist_track_ids come from get_playlist and are "not track IDs". The description restates that same distinction rather than adding new meaning, so it sits at the baseline. It does not explain batch semantics (all-or-nothing vs. partial removal) for the array parameter.

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?

"Remove entries from a playlist the user owns" gives a specific verb and resource, and the second sentence clarifies the identifier semantics (playlist_track_id, not track ID), which meaningfully separates this from a track-level removal. It never names a sibling such as move_playlist_tracks or delete_playlist, so the differentiation is behavioral rather than explicit.

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 knows this is the removal operation, and "a playlist the user owns" signals an ownership prerequisite. There is no statement of when to prefer this over move_playlist_tracks or delete_playlist, and no note on what happens if an ID is invalid.

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