spotify-library-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_playlistsA | List all playlists in the user's library (owned and followed). |
| get_playlistB | Get a playlist's details and its full track list. |
| create_playlistC | Create a new playlist for the user. |
| update_playlistB | Rename a playlist or change its description/visibility. |
| add_tracksA | Add tracks (ids or spotify:track: URIs) to a playlist, skipping ones already present. |
| remove_tracksC | Remove tracks from a playlist. |
| delete_playlistA | Remove a playlist from the user's library (unfollow). Irreversible for owned playlists. |
| merge_playlistsA | Merge several playlists into one (existing target or a new one), deduplicating tracks. Optionally delete sources. |
| find_trackA | Find one track, verifying the artist is on the result (avoids karaoke/cover mismatches). Returns null if no verified match. |
| save_tracksB | Add tracks to the user's Liked Songs. |
| remove_saved_tracksC | Remove tracks from Liked Songs. |
| get_search_budgetA | Remaining /search calls for today, cache size, and whether a Spotify search ban is active. Check before bulk searching. |
| get_api_limitsA | What this Spotify app can and cannot do (endpoints removed/renamed by Spotify for new apps). |
| summarize_playlistB | Stats for one playlist: runtime, top artists, decades, duplicates, over-representation. |
| summarize_libraryA | Whole-library health: liked songs in no playlist, stale/empty playlists, cross-playlist overlaps, per-playlist counts, liked-songs stats. Use before any reorganisation. |
| find_in_playlistsA | Which of the user's playlists contain a track (by name/artist substring, id, or uri); also whether it is Liked. |
| dedupe_reportB | Duplicate tracks (same artist + title, ignoring remaster/edit suffixes) inside each playlist, with ids to remove. |
| playlist_diffC | Tracks only in A, only in B, and shared count. |
| snapshot_libraryA | Save a full snapshot of all playlists + liked songs to disk (backup; enables changes_since). |
| list_snapshotsB | List saved snapshots. |
| changes_sinceA | What changed since a snapshot (default: latest): playlists created/deleted/renamed, tracks added/removed per playlist, likes added/removed. |
| rediscoverB | Liked songs from years ago that no longer appear in top tracks or recent plays — forgotten favourites, spread across artists. |
| get_saved_tracksB | All tracks the user has Liked. |
| searchD | Search Spotify. |
| get_top_tracksC | The user's most-played tracks. |
| get_top_artistsC | The user's most-played artists. |
| get_recently_playedD | Recently played tracks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools have a clear resource-and-action boundary: playlist operations, Liked Songs operations, search, snapshots, and stats are generally easy to tell apart. A few pairs such as search/find_track and dedupe_report/summarize_playlist overlap conceptually, but the descriptions clarify their distinct purposes.
The dominant pattern is verb_noun: list_playlists, create_playlist, add_tracks, remove_saved_tracks, get_top_tracks. Minor outliers like playlist_diff, changes_since, and rediscover break the pattern slightly but do not make the set confusing.
27 tools is on the high side, and several reporting, snapshot, and utility tools overlap in broad purpose. The platform supports a wide library-management workflow, so most tools are defensible, but the set would benefit from some consolidation.
The set covers playlist CRUD, liked-songs management, search, library summaries, deduplication, backups, and listening history. Missing playlist operations like reordering tracks is a noticeable but non-critical gap; the core workflows do not dead-end.