Related Servers

Many tools have genuinely distinct purposes and the descriptions include explicit decision guides (search vs search_deep vs search_fresh vs search_by_isrc vs whats_new; get_now_playing vs get_currently_playing), which helps a lot. However, there are several near-duplicate clusters (pin_playlist/follow_playlist, unpin_playlist/unfollow_playlist, multiple duplicate-detection tools, add_to_playlist/batch_add_to_playlist/merge_playlists/copy_playlist/move_items_between_playlists) that create real selection ambiguity. Boundaries are only disentangled by reading long prose, not by name.

The overwhelming majority of tools follow a snake_case verb_noun pattern (get_saved_tracks, create_playlist, add_to_playlist, remove_from_library, export_library_json). A handful deviate (whats_new, spotify_doctor, call_tool, play_from_search, schedule_wind_down), but these are readable and mostly intentional, so the convention is only mildly broken.

131 tools is an extreme surface far beyond what any agent can hold in context, and the server itself acknowledges this with dispatcher tools (find_tool, inspect_tool, call_tool, enable_toolset) built to work around its own size. The mass includes deprecated shims and many rarely-needed one-off utilities. This is a textbook over-scoped surface.

Coverage of the Spotify domain is remarkably thorough: playback, queue, devices, playlists (full CRUD plus transform ops), library CRUD, search variants, exports, backups, restore, undo, and diagnostics are all present, with no obvious core lifecycle gaps. The main shortfalls are deprecated/unavailable operations (get_user_profile, get_user_playlists_by_id, artist follow) that are documented as dead rather than removed, plus the sheer redundancy diluting the surface.