Skip to main content
Glama

skip_tracks

Skip multiple tracks in Spotify playback. Control music flow by specifying how many songs to advance, adjusting playback without interrupting your listening session.

Instructions

Skip multiple tracks at once
Args:
    num_skips: Number of tracks to skip (default: 1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
num_skipsNo

Implementation Reference

  • main.py:139-147 (handler)
    MCP tool handler and registration for 'skip_tracks'. Infers schema from function signature (num_skips: int default 1). Delegates execution to SpotifyClient.skip_track.
    @mcp.tool()
    async def skip_tracks(num_skips: int = 1) -> str:
        """
        Skip multiple tracks at once
        Args:
            num_skips: Number of tracks to skip (default: 1)
        """
        return await client.skip_track(num_skips)
  • Core implementation logic in SpotifyClient: skips n tracks by repeatedly calling Spotify API next_track.
    async def skip_track(self, n: int = 1) -> str:
        """
        Skip multiple tracks in the queue.
        - n: Number of tracks to skip (default: 1)
        """
        try:
            for _ in range(n):
                self.sp.next_track()
            return f"Skipped {n} tracks successfully"
        except Exception as e:
            return f"Error skipping tracks: {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 lacks behavioral details. It states the action but doesn't disclose effects (e.g., whether it advances playback, requires active playback, or interacts with queue), leaving critical operational context unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the core purpose, followed by parameter details in a structured 'Args:' section. It avoids redundancy, though the formatting could be more polished for readability.

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 tool with no annotations, no output schema, and low schema coverage, the description is insufficient. It covers basic purpose and parameters but misses behavioral context, return values, and integration with sibling tools, leaving significant gaps for effective use.

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 0%, but the description compensates by explaining the single parameter 'num_skips' as 'Number of tracks to skip' with a default value. This adds meaning beyond the bare schema, though it doesn't detail constraints like valid ranges.

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 verb ('skip') and resource ('tracks'), specifying it handles multiple tracks at once. It distinguishes from sibling 'next_track' by indicating batch skipping capability, though it doesn't explicitly contrast them.

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?

No guidance is provided on when to use this tool versus alternatives like 'next_track' or 'previous_track'. The description implies usage for skipping multiple tracks but offers no context on prerequisites, constraints, or typical scenarios.

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