spotify-mcp-server

add_to_playlist

Add tracks to an existing Spotify playlist. Automatically batches track URIs to comply with the Spotify API 100-track limit.

Instructions

Add one or more tracks to an existing Spotify playlist.

Handles batching automatically (Spotify API limit: 100 tracks per request).

Parameters

playlist_id : str Spotify playlist ID or full URI. track_uris : list[str] Spotify track URIs or bare track IDs.

Returns

dict Keys: playlist_id (str), tracks_added (int).

Raises

ValueError If track_uris is empty. spotipy.SpotifyException Propagated if the Spotify API returns a non-2xx response.

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": "add_to_playlist"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It transparently discloses batching (100 tracks per request), error handling (ValueError for empty track_uris, SpotifyException propagation), and return format. However, it omits permission requirements (e.g., playlist ownership/collaboration) which are relevant 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 well-structured with clear sections for Parameters, Returns, and Raises. No fluff, every section adds necessary info, and it is appropriately concise for the tool's complexity.

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 covers purpose, parameters, returns, and exceptions, making it fairly complete for a simple tool. However, it lacks context about prerequisites like playlist access/ownership, and does not clarify overlap with search_and_add, leaving minor gaps.

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

Parameters5/5

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

The description provides detailed parameter documentation beyond the input schema, including accepted formats ('Spotify playlist ID or full URI', 'track URIs or bare track IDs'). Since schema description coverage is 0%, this fully compensates and enhances meaning.

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 'Add one or more tracks to an existing Spotify playlist', using a specific verb and resource. This distinguishes it from siblings like add_to_queue (adds to queue) and create_playlist (creates new playlist).

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?

The description implies the tool is for adding tracks to playlists but does not explicitly specify when to use it over alternatives like add_to_queue or search_and_add. No exclusion or alternative guidance is provided, making usage context clear only by implication.

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

Deploy Server