Spotify MCP Server

by jamiew

Overview Schema Source Related Servers Discussions Admin

Python

Local

Remove Tracks from Playlist

remove_tracks_from_playlist

Destructive

Remove tracks or podcast episodes from a Spotify playlist by providing the playlist ID and track or episode URIs.

Instructions

Remove tracks or podcast episodes from a playlist.

Args:
    playlist_id: Playlist ID
    track_uris: Track or episode URIs/URLs to remove. Bare IDs are tracks.

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

Input Schema

Name	Required	Description	Default
`track_uris`	Yes
`playlist_id`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`snapshot_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.1Jun 2, 2026

removedOutput schema / additionalProperties

Removed value: -{
-  "type": "string"
-}

addedOutput schema / description

Added value: +"Result of a state-changing operation."

addedOutput schema / properties

Added value: +{
+  "message": {
+    "title": "Message",
+    "type": "string"
+  },
+  "snapshot_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Snapshot Id"
+  },
+  "status": {
+    "title": "Status",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "status",
+  "message"
+]

changedOutput schema / title

Previous value: -"remove_tracks_from_playlistDictOutput"New value: +"ActionResult"

Changed4 schema fields changedv1.0.0Jan 2, 2026

addedOutput schema / additionalProperties
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "additionalProperties": {
-      "type": "string"
-    },
-    "title": "Result",
-    "type": "object"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

changedOutput schema / title

Previous value: -"remove_tracks_from_playlistOutput"New value: +"remove_tracks_from_playlistDictOutput"

First observedAug 18, 2025

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this as a destructive, non-idempotent, open-world mutation, so the safety profile is carried. The description adds a useful behavioral note that bare IDs are interpreted as tracks, but says nothing about required scopes/auth, whether removing a non-existent track errors or silently succeeds, or how positions shift after removal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One-line purpose statement followed by two tight argument notes; nothing is padded or redundant. The Args block format is conventional and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explained, and annotations cover the mutation risk. However, for a destructive playlist mutation with 0% schema coverage, missing scope/permission and edge-case behavior leaves the agent with real gaps before calling it.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and only partly meets it. It labels playlist_id and describes track_uris as accepting track/episode URIs or URLs plus bare IDs, but gives no URI format example, no guidance on array size limits, and no note about duplicate handling.

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 ('Remove') and resource ('tracks or podcast episodes from a playlist'), which clearly separates it from remove_saved_tracks and remove_saved_episodes. It stops short of naming those siblings explicitly, but the 'from a playlist' scoping makes the target unambiguous.

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 implied by the resource scope — you use it to edit playlist membership, not the user's saved library — but there is no explicit when-to-use or when-not-to-use guidance, and no mention of reorder_playlist as the alternative for rearranging rather than deleting entries.

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

Deploy Server