Skip to main content
Glama

next_track

Skip to the next track in your Spotify queue to continue playback without interruption.

Instructions

Skip to next track in queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:44-47 (handler)
    FastMCP tool handler for 'next_track'. Registers the tool and executes by delegating to SpotifyClient.next_track().
    @mcp.tool()
    async def next_track() -> str:
        """Skip to next track in queue"""
        return await client.next_track()
  • SpotifyClient helper method implementing next_track logic using spotipy library.
    async def next_track(self) -> str:
        """
        Skip to the next track.
        """
        try:
            self.sp.next_track()
            return "Skipped to next track"
        except Exception as e:
            return f"Error skipping track: {str(e)}"
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 only states the action without behavioral details. It doesn't disclose whether this requires specific permissions, affects playback state, has side effects (e.g., updating queue), or any rate limits. 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 front-loaded with the core action 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.

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally complete but lacks behavioral context for a mutation operation. It states what the tool does but not how it behaves or what to expect, leaving gaps in understanding.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 'Skip to next track in queue' clearly states the action (skip) and resource (next track in queue) with specific verb+resource construction. It distinguishes from sibling tools like 'previous_track' (backward navigation) and 'skip_tracks' (which might skip multiple tracks).

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 wanting to advance playback, but provides no explicit guidance on when to use this versus alternatives like 'skip_tracks' or 'previous_track', nor any prerequisites (e.g., requires active playback). It's adequate but lacks sibling differentiation 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/ashwanth1109/mcp-spotify'

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