MCP server for controlling Spotify playback and accessing user music data
Spotify MCP has 15 tools with basic naming and descriptions, but significant quality gaps. Tool names follow verb_noun convention (play_*, get_*, etc.), which is good. However, descriptions are minimal (10-30 chars), well below the 50-200 char baseline for LLM-optimized tools. Most critically, input schemas are present but parameter descriptions are sparse or missing context. For example, 'playlist_name' lacks guidance on whether partial matches work or exact names required. No output schemas documented. Error handling is minimal, tools raise generic exceptions without recovery guidance. No tool annotations (readOnlyHint/destructiveHint) despite clear READ/WRITE distinction. The codebase shows try-catch blocks that log errors but don't guide the LLM on next steps.
Add a track to the active device's queue
get the currently playing artist and song
Return the user's recently played tracks
list the users playlists
skip to next track on active device
pause playback on active device
play a public playlist given it's name
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., playlist_id, track_uri). Baseline requires 100% of A+ tools to document return types.
Descriptions are 10-30 characters, far below the 50-200 char baseline for LLM-optimized tools. E.g., 'play a song on spotify given its unique uri' lacks context on when to use vs play_song_by_artist_song, what happens on error, or whether the URI must be exact.
Parameter descriptions are missing or trivial. 'playlist_name' has no guidance on exact vs partial match, case sensitivity, or what happens if multiple playlists share a name. LLMs cannot infer these constraints.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | <=2025-11-25 | v2 |
play a song on spotify given its artist and song
play a song on spotify given its unique uri
Play the user's liked songs
play a user's playlist given its name
skip to previous track on active device
start playback on active device
Toggle shuffle off active device
Toggle shuffle on active device
No error recovery guidance. Tools raise generic exceptions ('Failed to play song: {str(e)}') without telling the LLM what to do next. Should indicate: is this retryable? Should the user check device status? Is the URI invalid?
No tool annotations (readOnlyHint/destructiveHint). Code clearly marks tools as READ_ONLY or WRITE, but this is not exposed in the MCP schema. LLMs cannot reason about side effects or plan safely.