MCP server providing Spotify API integration with playback control, playlist management, search, and user profile capabilities
mcp-spotify has a large tool surface (38 tools) with structured schemas and descriptions present for most tools. However, there are significant gaps: (1) Input schemas use raw object shapes rather than proper JSON Schema with explicit type declarations visible in the schema field itself; (2) descriptions are adequate but generic, ranging 50-150 chars with minimal LLM optimization; (3) no error handling guidance or recovery paths documented; (4) no output schemas documented; (5) parameter descriptions lack format constraints, ranges, and validation rules; (6) no tool annotations (readOnly, destructive, idempotent hints); (7) composition is reasonable but several tools could be batch variants. The server follows basic naming conventions (verb_noun) and all 38 tools are explicitly registered with Zod schemas, which is a positive. However, the schema definitions are not fully visible in request schemas, they are defined as separate Zod objects (GetPlaybackStateInputRawShape, etc.) but the request handler receives only the raw object shape without type enforcement visible at the tool registration level.
Add an item to the user's playback queue.
Add one or more items to a user's playlist.
Change a playlist's name and public/private status, and collaborative status for the user's playlists.
Check to see if the current user is following a specified playlist.
Check to see if the current user is following one or more artists or other Spotify users.
Check if one or more tracks is already saved in the current Spotify user's 'Liked Songs' library.
No output schemas documented. Tools return JSON objects but LLMs cannot see the structure of response fields. This forces agents to infer outputs and risks misaligned downstream tool calls.
Parameter descriptions lack format constraints, ranges, and validation rules. E.g., 'position_ms' has no minimum/maximum; 'market' has no enum of valid codes; 'limit' has no bounds. LLMs will guess or pass invalid values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 58 | 2025-06-18+ | v2 |
| 2026-03-09 | D | 54 | - | v1 |
Add the current user as a follower of one or more artists or other Spotify users.
Add the current user as a follower of a playlist or remove the current user as a follower of a playlist.
Get the Spotify authentication link for Users who are not authenticated, which the user must visit to authenticate.THE LINK MUST BE COPIED FROM TERMINAL, DO NOT INCLUDE SPACES
Get information about a user's available Spotify Connect devices. Some device models are not supported and will not be listed.
Get detailed profile information about the current user (including email).
Get the current user's top tracks or artists based on calculated affinity.
Get the track or episode currently being played on the user's Spotify account.
Get the current user's followed artists.
Get information about the user's current playback state, including track or episode, progress, and active device.
Get full details of a playlist owned or followed by the current user.
Get full details of the items of a playlist owned or followed by the current user.
Get tracks from the user's recently played tracks.
Get a list of the songs saved in the current Spotify user's 'Liked Songs' library.
Get Spotify catalog information about multiple tracks identified by their unique Spotify IDs.
Get Spotify catalog information about a single track identified by its unique Spotify ID.
Get public profile information about a Spotify user.
Get the user's current playback queue.
Check if the user is authenticated with Spotify
Pause playback on the user's account. Premium only.
Remove one or more tracks from the current user's 'Liked Songs' library.
Save one or more tracks to the current user's 'Liked Songs' library.
Get Spotify catalog information about artists, tracks, albums, playlists, shows, episodes, or audiobooks that match a keywords.
Seeks to the given position in the user's currently playing track. Premium only.
Set the volume for the user's current playback device.
Set the repeat mode for playback on the user's account.
Skips to the next track in the user's queue. Premium only.
Skips to the previous track in the user's queue. Premium only.
Start a new context or resume current playback on the user's active device. Provide context_uri (album/playlist URI) OR uris (comma-separated track URIs). Premium only.
Toggle shuffle playback on the user's account.
Transfer playback to a new device and optionally begin playback. Provide a device ID. Note: This only works for Spotify Premium users.
Remove the current user as a follower of one or more artists or other Spotify users.
Either reorder or replace items in a playlist depending on the request's parameters.
No error handling guidance or recovery paths. Tools have no documented error responses, retry guidance, or actionable error messages. When a call fails, the agent has no recovery strategy.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe read-only tools from destructive write tools at a glance, risking unsafe tool selection ordering.
Some tool names contain 'and' or dual responsibilities. E.g., 'follow-or-unfollow-playlist' does two opposite actions; 'follow-artists-or-users' handles two entity types. These should be split into separate tools for clarity.
Pagination not consistently implemented. Several list tools (get-playlist-items, get-followed-artists, search-items) accept limit/offset but responses do not document total counts or next_cursor, making pagination planning difficult for agents.
get-auth-link description contains a warning in all caps ('THE LINK MUST BE COPIED FROM TERMINAL, DO NOT INCLUDE SPACES') that should be a formal constraint or error handling pattern, not prose.