Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

resumePlayback

Resume Spotify music playback on your active device to continue listening where you left off.

Instructions

Resume Spotify playback on the active device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdNoThe Spotify device ID to resume playback on

Implementation Reference

  • The handler function for the 'resumePlayback' tool. It destructures the optional deviceId from args, calls handleSpotifyRequest to invoke spotifyApi.player.startResumePlayback 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.startResumePlayback(deviceId || '');
      });
    
      return {
        content: [
          {
            type: 'text',
            text: 'Playback resumed',
          },
        ],
      };
    },
  • Zod input schema for the 'resumePlayback' tool, defining an optional 'deviceId' string parameter.
    schema: {
      deviceId: z
        .string()
        .optional()
        .describe('The Spotify device ID to resume playback on'),
    },
  • src/index.ts:12-14 (registration)
    Registers the 'resumePlayback' tool (included in playTools) with the MCP server by calling server.tool() for each tool in the spread array.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
  • src/play.ts:369-369 (registration)
    The 'resumePlayback' tool object is added to the exported playTools array, which is later imported and registered in index.ts.
    resumePlayback,
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'on the active device' which adds some context about scope, but fails to address critical aspects like authentication requirements, rate limits, error conditions (e.g., no active device), or what happens if playback is already resumed. 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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information immediately.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (success/failure indicators), error handling, or important behavioral constraints. The context signals indicate this is a simple tool, but the description should still address basic operational aspects.

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 already documents the single parameter 'deviceId' with its description. The tool description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Resume') and target ('Spotify playback on the active device'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'pausePlayback' or 'playMusic', which would require a 5.

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 like 'playMusic' or 'pausePlayback', nor does it mention prerequisites such as needing an active device or playback session. It only states what the tool does, not when it's appropriate.

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