mcp-spotify-free

Overview Schema Source Related Servers Discussions Admin

Skip Next

skip_next

Skips playback to the next track on Spotify Connect devices, including for free accounts; optionally specify the target device.

Instructions

Skip to the next track.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skip_next"
  }
}

Input Schema

Name	Required	Description	Default
`device`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Oct 23, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it says nothing about required auth/session state, what happens at the end of a queue, or that it mutates playback state. 'Skip' implies a state change, but the operational preconditions are undisclosed.

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?

One short, front-loaded sentence with no filler. It is efficient, though its brevity is also the source of the missing detail rather than a deliberate trade-off.

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?

The tool is simple and an output schema covers return values, so grand detail isn't needed. However, the undocumented 'device' parameter and unstated session/playback preconditions leave real gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single 'device' parameter (an untyped free string with an empty default) is never mentioned in the description. The agent cannot tell whether it expects a device ID, name, or whether omitting it targets the active device.

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?

States a specific verb and resource: 'Skip to the next track.' Combined with the name, an agent can tell it apart from siblings like skip_previous and play_track without opening the schema. It stops short of explicitly differentiating, but the action is unambiguous.

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 on when to use this versus play_track, resume_playback, or skip_previous, and no prerequisites such as an active Spotify session or playing device. The agent must infer that playback is already underway.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.