skip_to_next
Skip to the next track in Spotify playback to navigate playlists, skip unwanted songs, or control music progression during listening sessions.
Instructions
Skip to the next track in the user's playback queue or playlist.
🎯 USE CASES: • Skip songs that don't match current mood or activity • Navigate through playlists and albums quickly • Build custom music control interfaces • Create voice-activated skip commands • Implement automatic skipping based on user preferences
📝 WHAT IT RETURNS: • Information about the new track that started playing • Updated playback position reset to beginning • Queue information showing remaining tracks • Confirmation of successful skip operation • Device state with new playback status
🔍 EXAMPLES: • "Skip to the next song" • "Play the next track in this playlist" • "Move forward to the next song" • "I don't like this song, skip it"
🎵 SKIP BEHAVIOR: • Follows playlist/album order when not shuffled • Respects shuffle mode for random progression • May trigger repeat behavior at end of playlists • Updates listening history and statistics • Can trigger discovery algorithms for similar music
⚠️ REQUIREMENTS: • Valid Spotify access token with user-modify-playback-state scope • Active playback session with available next track • User must have appropriate device control permissions
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Spotify access token for authentication | |
| deviceId | No | Spotify device ID (optional, uses active device if not specified) |
Implementation Reference
- src/mcp/tools/playback.ts:207-250 (handler)MCP tool registration for 'skip_to_next' including schema, description, and handler function that delegates to SpotifyService.skipToNext
skip_to_next: { title: "Skip to Next Track", description: `Skip to the next track in the user's playback queue or playlist. 🎯 USE CASES: • Skip songs that don't match current mood or activity • Navigate through playlists and albums quickly • Build custom music control interfaces • Create voice-activated skip commands • Implement automatic skipping based on user preferences 📝 WHAT IT RETURNS: • Information about the new track that started playing • Updated playback position reset to beginning • Queue information showing remaining tracks • Confirmation of successful skip operation • Device state with new playback status 🔍 EXAMPLES: • "Skip to the next song" • "Play the next track in this playlist" • "Move forward to the next song" • "I don't like this song, skip it" 🎵 SKIP BEHAVIOR: • Follows playlist/album order when not shuffled • Respects shuffle mode for random progression • May trigger repeat behavior at end of playlists • Updates listening history and statistics • Can trigger discovery algorithms for similar music ⚠️ REQUIREMENTS: • Valid Spotify access token with user-modify-playback-state scope • Active playback session with available next track • User must have appropriate device control permissions`, schema: createSchema({ token: commonSchemas.token(), deviceId: commonSchemas.deviceId(), }), handler: async (args: any, spotifyService: SpotifyService) => { const { token, deviceId } = args; return await spotifyService.skipToNext(token, deviceId); }, }, - src/spotify.ts:674-682 (handler)Core implementation of skipToNext in SpotifyService class, which makes POST request to Spotify API endpoint /me/player/next
async skipToNext( token: string, deviceId: string | null = null ): Promise<void> { const endpoint = deviceId ? `me/player/next?device_id=${deviceId}` : "me/player/next"; return await this.makeRequest<void>(endpoint, token, {}, "POST"); } - src/mcp/tools/index.ts:22-36 (registration)Aggregation of all tools including playbackTools (which contains skip_to_next) into the central allTools registry used by the MCP server
export const allTools: ToolsRegistry = { ...albumTools, ...artistTools, ...trackTools, ...playlistTools, ...playbackTools, ...userTools, ...searchTools, }; - src/mcp/tools/playback.ts:242-245 (schema)Input schema for skip_to_next tool using common token and deviceId schemas
schema: createSchema({ token: commonSchemas.token(), deviceId: commonSchemas.deviceId(), }),