Skip to main content
Glama
marcelmarais

Spotify MCP Server

by marcelmarais

pausePlayback

Pause music playback on Spotify devices. Control audio streaming by stopping playback on active or specified devices.

Instructions

Pause Spotify playback on the active device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoThe Spotify device ID to pause playback on

Implementation Reference

  • The handler function for the pausePlayback tool. It extracts the deviceId from args, calls handleSpotifyRequest to pause playback via Spotify API, and returns a success message.
    handler: async (args, _extra: SpotifyHandlerExtra) => {
      const { deviceId } = args;
    
      await handleSpotifyRequest(async (spotifyApi) => {
        await spotifyApi.player.pausePlayback(deviceId || '');
      });
    
      return {
        content: [
          {
            type: 'text',
            text: 'Playback paused',
          },
        ],
      };
    },
  • Zod input schema defining optional deviceId parameter for the pausePlayback tool.
    schema: {
      deviceId: z
        .string()
        .optional()
        .describe('The Spotify device ID to pause playback on'),
    },
  • src/play.ts:499-510 (registration)
    The pausePlayback tool is registered by being included in the exported playTools array, likely used for MCP tool registration.
    export const playTools = [
      playMusic,
      pausePlayback,
      skipToNext,
      skipToPrevious,
      createPlaylist,
      addTracksToPlaylist,
      resumePlayback,
      addToQueue,
      setVolume,
      adjustVolume,
    ];
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 of behavioral disclosure. It states the action but does not describe effects like whether playback can be resumed, if it requires specific permissions, or what happens if no active device exists. This leaves gaps for a mutation tool with no 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 waste. It is front-loaded with the core purpose and appropriately sized for the tool's complexity, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool has no annotations, no output schema, and a simple parameter structure, the description is minimally adequate but lacks details on behavioral outcomes and error conditions. It covers the basic purpose but does not fully address the context needed for reliable use by an agent.

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%, with the single parameter 'deviceId' documented in the schema. The description does not add any parameter details beyond what the schema provides, such as clarifying default behavior if 'deviceId' is omitted. Baseline 3 is appropriate when 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 ('Pause') and target resource ('Spotify playback on the active device'), distinguishing it from sibling tools like 'resumePlayback' and 'playMusic'. It precisely communicates what the tool does 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 Guidelines3/5

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

The description implies usage context by specifying 'on the active device', but does not explicitly state when to use this tool versus alternatives like 'resumePlayback' or 'playMusic'. No guidance is provided on prerequisites, such as requiring active playback or device availability.

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/marcelmarais/spotify-mcp-server'

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