Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_from_playlist

Destructive

Remove up to 100 tracks or episodes from a Spotify playlist, targeting specific occurrences by position and previewing changes with dry run.

Instructions

Remove tracks or episodes from a playlist. Max 100 entries per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYesURIs to remove; use { uri, positions } to target specific occurrences of a repeated URI
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
playlist_idYesPlaylist ID
snapshot_idNoApply the removal against this playlist version instead of the latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / uris / items / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "properties": {
-      "positions": {
-        "items": {
-          "maximum": 9007199254740991,
-          "minimum": 0,
-          "type": "integer"
-        },
-        "minItems": 1,
-        "type": "array"
-      },
-      "uri": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "uri",
-      "positions"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "properties": {
+      "positions": {
+        "description": "0-based index into the playlist's current item order (0 = the first item).",
+        "items": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "uri": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "uri",
+      "positions"
+    ],
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed7 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • addedInput schema / properties / snapshot_id
      Added value: +{
+  "description": "Apply the removal against this playlist version instead of the latest",
+  "type": "string"
+}
    • changedInput schema / properties / uris / description
      Previous value: -"URIs to remove"New value: +"URIs to remove; use { uri, positions } to target specific occurrences of a repeated URI"
    • addedInput schema / properties / uris / items / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "properties": {
+      "positions": {
+        "items": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "uri": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "uri",
+      "positions"
+    ],
+    "type": "object"
+  }
+]
    • removedInput schema / properties / uris / items / type
      Removed value: -"string"
    • addedInput schema / properties / uris / maxItems
      Added value: +100
  4. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The destructiveHint annotation already carries the safety profile, lowering the bar. The description adds the tracks/episodes scope and the per-call volume cap, but the cap duplicates the schema's maxItems: 100 and it discloses nothing about dry_run, snapshot preconditions, or undo availability.

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?

Two short sentences, action first, no filler. The second sentence repeats a schema constraint, which is mild redundancy rather than bloat.

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?

Adequate minimum: a destructive mutation whose parameters are fully documented by the schema and whose safety profile is covered by annotations, with no output schema needed. It stops short of useful operational context such as snapshot conflict behavior or recovery paths.

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 all four parameters (including the uri/positions targeting form and dry_run) are already explained. The description only restates the 100-entry ceiling, adding no semantics beyond the schema; 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?

Specific verb (remove) plus resource (tracks or episodes from a playlist), and it correctly notes both content types. It does not distinguish itself from adjacent siblings such as remove_duplicate_playlist_items or playlist_subtract, so it is clear but undifferentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative routing is given. The description never tells the agent why it would pick this over remove_duplicate_playlist_items, playlist_subtract, or batch_add_to_playlist, leaving selection entirely to inference.

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

Deploy Server

Other Tools