Spotify MCP Server

play_playlist

Start playback of a Spotify playlist by specifying its name, with optional device selection for targeted audio output.

Instructions

Play a Spotify playlist by name

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": {
      "playlistName": "<playlistName>"
    },
    "name": "play_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`playlistName`	Yes	Name of the playlist to play
`deviceId`	No	Optional device ID to play on

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 14, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Play' implies a write/mutation operation, it doesn't specify whether this requires specific permissions, what happens if the playlist isn't found, whether playback interrupts current audio, or any rate limits. This leaves significant behavioral gaps 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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple tool and gets straight to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, return values, error conditions, or behavioral constraints. Given the complexity of media playback and the lack of structured data, more context is needed.

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 both parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (playlistName and optional deviceId). This meets the baseline for high schema coverage but doesn't provide extra value.

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 clearly states the action ('Play') and resource ('a Spotify playlist by name'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like play_album or play_track, which perform similar playback actions on different resource types.

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 provides no guidance on when to use this tool versus alternatives like play_album, play_track, or play_random_song. It also doesn't mention prerequisites such as needing an active Spotify session or available devices, which are critical context for playback tools.

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

Deploy Server