Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

skipToNext

Advances playback to the next track in your current Spotify queue. Use this tool to skip songs during listening sessions.

Instructions

Skip to the next track in the current Spotify playback queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoThe Spotify device ID to skip on

Implementation Reference

  • The handler function for the 'skipToNext' tool. It extracts the optional deviceId from args, calls handleSpotifyRequest to execute spotifyApi.player.skipToNext on the specified or default device, and returns a success message.
    handler: async (args, _extra: SpotifyHandlerExtra) => {
      const { deviceId } = args;
    
      await handleSpotifyRequest(async (spotifyApi) => {
        await spotifyApi.player.skipToNext(deviceId || '');
      });
    
      return {
        content: [
          {
            type: 'text',
            text: 'Skipped to next track',
          },
        ],
      };
    },
  • The Zod input schema for the 'skipToNext' tool, defining an optional deviceId string.
    schema: {
      deviceId: z
        .string()
        .optional()
        .describe('The Spotify device ID to skip on'),
    },
  • src/index.ts:12-14 (registration)
    Registration of all tools, including skipToNext from playTools, by calling server.tool() for each.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
  • src/play.ts:365-365 (registration)
    skipToNext tool is included in the exported playTools array.
    skipToNext,
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the action but does not disclose behavioral traits such as whether it requires active playback, what happens if no next track exists, or if it affects the queue. This is a significant gap for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('skip to the next track') and context ('in the current Spotify playback queue'). There is no wasted verbiage, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral outcomes, error conditions, or what happens after skipping. For a tool that modifies playback state, more context is needed to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for the single parameter ('deviceId'), so the baseline is 3. The description does not add parameter details beyond the schema, but since there is only one optional parameter, the tool's purpose remains clear without extra semantics, justifying a score above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('skip to the next track') and the context ('in the current Spotify playback queue'), distinguishing it from sibling tools like 'skipToPrevious' (which goes backward) and 'pausePlayback' (which stops). It uses specific verbs and resources without being tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when the user wants to advance playback, but it does not explicitly state when to use this tool versus alternatives (e.g., 'skipToPrevious' for going back, 'playMusic' for starting playback). No exclusions or prerequisites are mentioned, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/makesh-kumar/spotify-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server