Skip to main content
Glama
ashwanth1109

Spotify MCP

by ashwanth1109
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

start_playback

Resume music playback on your active Spotify device. Use this tool to continue playing paused tracks or restart stopped playback.

Instructions

FastMCP tool to resume playback on the currently active Spotify device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:16-22 (handler)
    MCP tool handler for 'start_playback'. This is the function executed when the tool is called. It delegates to the SpotifyClient instance.
    @mcp.tool()
async def start_playback() -> str:
    """
    FastMCP tool to resume playback on the currently active Spotify device.
    """
    return await client.start_playback()
  • spotify.py:69-78 (helper)
    Core implementation of start_playback in SpotifyClient class. Calls spotipy's start_playback() method to resume playback.
    async def start_playback(self) -> str:
    """
    Resume playback on the currently active device.
    """
    try:
        self.sp.start_playback()
        return "Playback started successfully"
    except Exception as e:
        return f"Error starting playback: {str(e)}"
  • main.py:16-16 (registration)
    Registration of the 'start_playback' tool via FastMCP decorator.
    @mcp.tool()

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation (resuming playback) but doesn't disclose effects like whether it resumes from paused state or last position, potential errors if no device is active, or authentication requirements. This leaves significant gaps for a tool that likely interacts with user playback.

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 directly states the tool's purpose with no wasted words. It's front-loaded and appropriately sized for a simple tool with no parameters.

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 likely performs a mutation (resuming playback) with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects like error conditions, return values, or side effects, leaving the agent with incomplete context for safe invocation.

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 tool has zero parameters, and schema description coverage is 100%, so there's no need for parameter explanation in the description. The baseline for zero parameters is 4, as the description appropriately doesn't discuss non-existent inputs.

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 playback') and target resource ('currently active Spotify device'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'pause_playback' or 'start_playback_track' beyond the obvious verb difference, which prevents a perfect score.

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 'start_playback_track' or 'start_playlist_playback', nor does it mention prerequisites such as requiring an active device or playback state. 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/ashwanth1109/mcp-spotify'

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