Spotify
Connect agents to Spotify for music playback control. Search tracks, manage playlists, and control playback.
Available Tools
13 tools available in this integration
Spotify.GetTrackFromId Get information about a track
Spotify.AdjustPlaybackPosition Modify playback position within currently playing content
Spotify.SkipToPreviousTrack Skip to the previous track in the user's queue
Spotify.SkipToNextTrack Skip to the next track in the user's queue
Spotify.PausePlayback Pause the currently playing track
Spotify.ResumePlayback Resume the currently playing track
Spotify.StartTracksPlaybackById Start playback of a list of tracks (songs)
Spotify.GetPlaybackState Access user's current playback information including active device
Spotify.GetCurrentlyPlaying Get information about the user's currently playing track
Spotify.PlayArtistByName Play artist content and queue related selections
Spotify.PlayTrackByName Plays a song by name
Spotify.GetAvailableDevices Get the available devices
Spotify.Search Search Spotify catalog information
Why agent-optimized tools matter
Built for intent, not API schemas
Forcing the agent to juggle not only what you want to get done, but also how to operate all the APIs it needs to use is a recipe for disaster. Agent-optimized tools keep the agent focused on the work at hand, not ID hunting.
Up to 100x fewer tokens
Context bloat is a serious problem that gets in the way of real work getting done with agents. Agent-optimized tools return only the fields the agent needs to get the job done, not the full API response. Up to 100x less token consumption on every call.
Coverage for the whole task
Most tasks take more than one action to finish. Agent-optimized tools cover the full sequence so the agent completes the workflow end to end, not just the first lookup.
Consistent at scale
Agent-optimized tools behave the same across every user, every run, every harness, every model, and every effort level. No need for the agent to spend time and tokens re-learning the API shape, it can focus on the task at hand. What works for one user holds up when serving thousands in production.
Your questions, answered
It's built around what an agent is trying to accomplish rather than mirroring Spotify's raw API. Fewer required parameters, far fewer tokens per call, and coverage for the whole task — so agents succeed more often.
Yes. The toolkit is exposed over an MCP gateway that any framework or MCP client can connect to, and we publish install guides for the editors and coding agents we document.
No. Arcade proxies API calls and does not persist your Spotify content. Where Spotify requires credentials, Arcade brokers them and stores them encrypted at rest — the model never sees them.
With Contextual Access policies: require human approval before consequential actions, redact sensitive fields on the way back, or restrict the scopes a given agent gets.
