Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_saved_items

Delete saved Spotify tracks, albums, shows, episodes, or audiobooks from your library in bulk using URIs; preview with dry_run before committing changes.

Instructions

Legacy per-type variant (kept for grandfathered app credentials that lack unified /me/library access). Prefer remove_from_library. Remove one or more items from the user's library. Accepts track, album, show, episode, and audiobook URIs (e.g. spotify:track:abc). Max 50. Set dry_run=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisYesSpotify URIs to remove
dry_runNoPreview only: show exactly which URIs would be removed without calling the API
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: show exactly which URIs would be removed without calling the API",
+  "type": "boolean"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal the legacy nature, supported URI types, the 50-item maximum, and the dry_run preview behavior. However, it does not explicitly describe side effects, required permissions, idempotency, or what happens on a real removal, which would be valuable for a mutation tool.

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?

The description is compact and front-loads the most important caveat (legacy variant, prefer remove_from_library) before the core action. Every sentence contributes useful information, and there is no filler or repetition.

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?

The description is largely complete for a moderately simple tool: it covers the action, supported inputs, limits, preview mode, and the preferred alternative. It does not explicitly describe the response or side effects, but the response_format parameter is documented in the schema, and no output schema exists to otherwise clarify return values.

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

Parameters4/5

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

The schema already has 100% parameter coverage, so the baseline is 3. The description adds value beyond the schema by enumerating accepted URI types (track, album, show, episode, audiobook) and giving a concrete format example (spotify:track:abc), which helps the agent form valid inputs. It also reinforces dry_run usage.

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?

The description clearly states a specific action ('Remove one or more items from the user's library') and specifies the resource. It also explicitly differentiates itself from the preferred sibling tool by labeling itself a 'Legacy per-type variant' and directing users to remove_from_library, making its purpose unmistakable.

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

Usage Guidelines5/5

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

The description gives explicit usage context: it is kept for grandfathered app credentials that lack unified /me/library access. It also names the preferred alternative ('Prefer remove_from_library'), giving an agent clear guidance on when to choose this tool versus the sibling.

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