Seek to a specific playback position by providing a target time in milliseconds. Use this to skip directly to any moment in the current track.
跳转到指定播放位置
| Name | Required | Description | Default |
|---|---|---|---|
| device_id | No | 设备ID（可选） | |
| position_ms | Yes | 目标位置（毫秒） |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it only states the action without mentioning prerequisites such as active playback, side effects on the current track, or potential failures. No extra context is added beyond the basic operation.
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?
The description is a single concise sentence that is entirely purposeful and front-loaded, with no filler. It communicates the essential operation in the simplest possible form.
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?
While the schema fully describes parameters, the description lacks any context about the need for active playback, device selection, or what happens on success/failure. It is adequate for a simple seek operation but does not provide richer operational context.
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?
Both parameters have schema descriptions covering 100% of the parameters, so the description adds no additional parameter semantics. The baseline score of 3 is appropriate because the schema already provides full parameter meaning.
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?
The description clearly states the action (jump/seek) and the target (specified playback position), effectively distinguishing it from playback control siblings like pause, next, and previous. The verb 'jump' precisely conveys a seek operation, and the resource is unmistakable.
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?
No guidance is provided on when to use this tool instead of alternatives such as spotify_next or spotify_play_song, leaving the agent to infer the appropriate context. There is no mention of prerequisites like active playback or device selection, nor any exclusionary conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.