Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_from_playlist

Remove tracks or episodes from a Spotify playlist using playlist ID and item URIs, up to 100 per call. Optionally preview changes with dry run before applying.

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. 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
  2. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It only says 'Remove' and repeats the max-100 constraint already present in the schema. It does not disclose mutability, irreversibility, permissions, snapshot behavior, or what a dry-run preview provides.

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, front-loaded sentences communicate the core operation and the batch limit with no filler. Every word contributes.

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?

The schema covers parameters well, but the overall tool context is incomplete for an unannotated mutation: no return-value expectations, no warning that removals are permanent, and no explanation of how snapshot_id or dry_run interact with the remove action.

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 the schema already documents playlist_id, uris, dry_run, and snapshot_id. The description adds only a high-level statement about removing tracks/episodes and a max limit already enforced by maxItems, so it adds little beyond the schema.

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 states a specific verb and resource: 'Remove tracks or episodes from a playlist.' It is clear and distinct from sibling tools like add_to_playlist or remove_from_library_by_playlist, though it could have explicitly differentiated itself from related removal variants such as remove_unavailable_playlist_items.

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?

The description gives no guidance on when to use this tool versus alternatives, no exclusions, and no mention of positional removal for repeated URIs. Sibling tools with overlapping semantics exist, but no routing or preference cues are provided.

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