Related Servers

Most tools target a clear resource+action pair (save_tracks vs check_saved_tracks vs get_saved_tracks, follow_artists vs check_following_artists), and descriptions explicitly cross-reference each other. The main soft spots are control_playback being a multi-action mega-tool that partly overlaps transfer_playback and add_to_queue, and the large family of save/remove/check/get library tools for six resource types that a hurried agent could mix up.

Nearly everything follows a verb_noun pattern (get_tracks, save_albums, remove_saved_shows, list_playlists, check_saved_episodes), with predictable get_/save_/remove_/check_ prefixes per resource. Minor deviations like get_me and control_playback (verb-only, multiplexed) are the only breaks in the pattern.

48 tools is heavy for a single MCP surface; the library-management matrix (get/save/remove/check for tracks, albums, shows, episodes, audiobooks, artists, playlists) alone accounts for ~20 tools. It mirrors the Spotify API faithfully, but many of these will rarely be selected and inflate the decision space for an agent.

Coverage is broad: playback control, queue, playlists with reorder, library CRUD across all media types, podcasts, audiobooks, and personalization. Gaps are mostly read-side detail endpoints — no get_show, get_episode, or get_audiobook metadata tools, and playlist deletion is only reachable via unfollow_playlist — but agents can work around these.