Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

pausePlayback

Pause Spotify playback on the active device to temporarily stop music without ending your session.

Instructions

Pause Spotify playback on the active device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoThe Spotify device ID to pause playback on

Implementation Reference

  • The async handler function for the pausePlayback tool, which pauses Spotify playback on the specified or active device using the Spotify API.
    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 for the pausePlayback tool, defining an optional deviceId parameter.
    schema: {
      deviceId: z
        .string()
        .optional()
        .describe('The Spotify device ID to pause playback on'),
    },
  • src/play.ts:362-371 (registration)
    The pausePlayback tool is included in the playTools array, which groups Spotify playback-related tools for export.
    export const playTools = [
      playMusic,
      pausePlayback,
      skipToNext,
      skipToPrevious,
      createPlaylist,
      addTracksToPlaylist,
      resumePlayback,
      addToQueue,
    ];
  • src/index.ts:12-14 (registration)
    All tools from playTools (including pausePlayback) are registered with the MCP server by calling server.tool for each.
    [...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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it states the action, it doesn't mention required permissions, whether this affects other devices, error conditions, or what happens if no active device exists. For a mutation tool with zero annotation coverage, this is insufficient.

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, clear sentence with zero wasted words. It's front-loaded with the core action and efficiently communicates the essential information without unnecessary elaboration.

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's moderate complexity (a mutation with one optional parameter) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose but lacks behavioral details like error handling or side effects, which are important for a playback control tool.

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 schema description coverage is 100%, so the parameter 'deviceId' is fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, but with only one parameter and high schema coverage, the baseline is appropriately met.

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 resource ('Spotify playback on the active device'), distinguishing it from sibling tools like 'playMusic' and 'resumePlayback'. 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 when playback needs to be paused, but doesn't explicitly state when to use this tool versus alternatives like 'resumePlayback' or 'skipToNext'. It provides basic context but lacks explicit guidance on prerequisites or exclusions.

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