Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

skipToPrevious

Go back to the previous track in your current Spotify playback queue. Control playback by specifying a device ID to skip tracks on your connected Spotify devices.

Instructions

Skip to the previous 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 'skipToPrevious' tool. It extracts the optional deviceId from arguments, uses handleSpotifyRequest to call the Spotify API's skipToPrevious method, and returns a success message.
      handler: async (args, _extra: SpotifyHandlerExtra) => {
        const { deviceId } = args;
    
        await handleSpotifyRequest(async (spotifyApi) => {
          await spotifyApi.player.skipToPrevious(deviceId || '');
        });
    
        return {
          content: [
            {
              type: 'text',
              text: 'Skipped to previous track',
            },
          ],
        };
      },
    };
  • The Zod input schema for the 'skipToPrevious' tool, defining an optional string parameter for deviceId.
    schema: {
      deviceId: z
        .string()
        .optional()
        .describe('The Spotify device ID to skip on'),
    },
  • src/play.ts:362-371 (registration)
    The 'skipToPrevious' tool is included in the playTools array, which is exported and later used for registration.
    export const playTools = [
      playMusic,
      pausePlayback,
      skipToNext,
      skipToPrevious,
      createPlaylist,
      addTracksToPlaylist,
      resumePlayback,
      addToQueue,
    ];
  • src/index.ts:12-14 (registration)
    Main registration loop in index.ts that registers all tools from playTools (including skipToPrevious) to the MCP server.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions needed, effects on queue/playback state, error conditions (e.g., no previous track), or response format. This is inadequate 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 with zero wasted words. It is front-loaded with the core purpose and appropriately sized for a simple tool, making it easy to parse quickly.

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 mutation nature (skip action), lack of annotations, and no output schema, the description is incomplete. It omits critical behavioral context like side effects, error handling, and response details, leaving significant gaps for agent understanding.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents the single parameter (deviceId). The description does not add any parameter-specific details beyond what the schema provides, such as when deviceId is required or default behavior. Baseline 3 is appropriate as the schema handles parameter documentation.

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 specific action ('Skip to the previous track') and resource ('current Spotify playback queue'), distinguishing it from sibling tools like skipToNext (next track) and pausePlayback/resumePlayback (playback control). It precisely defines the tool's function without ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., active playback), exclusions (e.g., no queue), or comparisons to siblings like skipToNext. Usage is implied but not explicitly defined.

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