Add a Spotify track to the current playback queue using its track URI. Optionally specify a device ID to target playback.
Add a track to the queue. Needs uri.
| Name | Required | Description | Default |
|---|---|---|---|
| uri | Yes | Track URI. | |
| device_id | No | Optional device ID from get_devices. |
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 must carry the full behavioral burden. It says only 'Needs uri' and reveals nothing about authentication, device context, mutation side effects, or what happens when a track is added to the queue.
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 very short and front-loads the action. The second sentence, 'Needs uri,' is redundant with the schema's required field, so it does not fully earn its place.
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?
The tool is simple and schema coverage is complete, so the purpose is minimally covered. However, with no annotations and no output schema, an agent gets no behavioral context about device targeting or queue semantics.
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 coverage is 100%, so the schema already documents both uri and device_id. The description's 'Needs uri' merely repeats the required field and adds no semantic detail beyond the schema.
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 and resource: 'Add a track to the queue.' This clearly separates it from siblings like add_to_playlist and play, but it does not explicitly name or contrast those alternatives.
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 on when to use this tool versus alternatives such as add_to_playlist, play, or play_liked. The description only states the basic action and the required parameter, leaving selection entirely implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.