Skip to the previous track during Spotify playback. Use when you need to go back to an earlier song or restart the current track.
Skip to previous track
| Name | Required | Description | Default |
|---|---|---|---|
| device_id | No | Optional: Device ID |
Changes observed during successful MCP inspections.
v1.2.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden, yet it only restates the action. It says nothing about auth requirements, error behavior when no previous track exists, or whether an optional device must be active.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single four-word sentence, front-loaded with the action, with no wasted tokens. Appropriate size for a trivial playback control.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, no-output action tool the description is close to adequate, but with zero annotations it should say something about prerequisites or failure modes to be fully self-contained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single optional device_id parameter, so the schema already documents it fully. The description adds no parameter meaning beyond that, matching the baseline for high-coverage schemas.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Skip') and resource ('previous track'), making the action immediately unambiguous. It does not explicitly differentiate from the sibling spotify_next, though the naming pair is self-evident.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the verb; there is no guidance on when this applies versus alternatives like spotify_next or spotify_transfer_playback, nor any note about playback needing to be active or what happens at the start of a queue.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.