Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

skip_next

Skip to the next track in your Spotify queue or context. Use for advancing playback without manual selection.

Instructions

Skip to the next track in the queue or context Also covers: batch skip via skip_n — See also: skip_n, skip_previous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
device_idNoTarget device ID
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects and prerequisites. It only states the action ('Skip to the next track') with no mention that this is a mutating playback operation, whether it requires active playback, or what happens if the queue is empty. The dry_run parameter is documented in the schema, not in the description.

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 primary purpose. The 'Also covers' fragment is grammatically awkward and slightly confusing, but the overall length is appropriate.

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?

For a simple playback-control tool with three optional parameters, the description gives the core action and sibling pointers. However, it omits behavioral context like side effects, error conditions (e.g., end of queue), and the ambiguity around skip_n makes it incomplete for an agent deciding between siblings.

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?

The input schema covers 100% of parameters with descriptions for dry_run, device_id, and response_format. The description adds no parameter-specific meaning, so the baseline 3 applies due to full 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 states the verb 'Skip' and the resource 'next track in the queue or context,' which clearly defines the core action. It distinguishes from skip_previous by naming it in 'See also,' though the relationship to skip_n is ambiguous: 'Also covers: batch skip via skip_n' could imply this tool covers batch skipping.

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 'See also: skip_n, skip_previous' line points to related siblings, and 'batch skip via skip_n' hints that batch skipping should be routed to skip_n. However, it never explicitly states when to choose skip_next over skip_n, and the phrasing is ambiguous about whether skip_next itself handles batch skips.

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

Deploy Server

Other Tools