MCP Claude Spotify

delete-playlist

Remove a playlist from your Spotify library without deleting it. Use the playlist ID to unfollow it while keeping the playlist available on Spotify.

Instructions

Unfollow a playlist (removes it from your library, but the playlist still exists on Spotify)

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": {
      "playlistId": "<playlistId>"
    },
    "name": "delete-playlist"
  }
}

Input Schema

Name	Required	Description	Default
`playlistId`	Yes	Spotify ID of the playlist to delete

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.0Sep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key non-obvious trait: this is a non-destructive unfollow, not a true deletion, so the playlist survives on Spotify. It does not mention idempotency, auth requirements, or what happens when the playlist is already unfollowed.

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?

One sentence, front-loaded with the actual operation, with the parenthetical immediately defusing the destructive connotation of the tool name. Nothing is wasted.

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?

For a one-parameter, no-output-schema mutation tool, the behavioral clarification is the main thing an agent needs, and it is present. Missing only auth/prerequisite context, which is minor given a dedicated auth-spotify sibling.

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 single parameter playlistId is already documented in the schema, so the description adds no parameter-level meaning. Baseline 3 is appropriate when the schema does this work.

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 states a specific verb (unfollow) and resource (playlist), and crucially corrects the misleading 'delete' in the tool name by clarifying the playlist is not destroyed. An agent can distinguish this from update-playlist, create-playlist, and remove-tracks-from-playlist without opening any schema.

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: use this to remove a playlist from the user's library while leaving it on Spotify. There is no explicit when-to-use, prerequisite (e.g. authentication via auth-spotify), or statement of alternatives such as update-playlist for renaming.

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