Rename a Spotify device by assigning a custom local label. Updates the sidecar name used by this server, since Spotify lacks a native rename endpoint.
Rename a device locally (sidecar label — Spotify has no rename endpoint).
| Name | Required | Description | Default |
|---|---|---|---|
| new_name | Yes | Friendly label | |
| device_id | Yes | Device id | |
| response_format | No | 'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object | concise |
Changes observed during successful MCP inspections.
v1.26.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does disclose the most critical trait: the rename is local-only and will not propagate to Spotify. However, it does not say whether the label persists across sessions, what happens when an unknown device_id is supplied, or whether other tools in the toolset (compare_devices, device_sync_state) reflect the new label.
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 10-word sentence with a tightly packed parenthetical that earns its place by explaining why the operation is local. The key scoping constraint is front-loaded ahead of any caveat, and every word carries information.
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 core operation and its key limitation are covered, which is sufficient for correct invocation in the common case. But with no output schema and no annotations, the sidecar lifecycle is left open: persistence, handling of unknown devices, and interaction with device-sync tooling are unaddressed, leaving an agent to guess at edge-case behavior.
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 all three parameters are already documented and the baseline is 3. The description adds some meaning by clarifying that new_name is a 'sidecar label' rather than a Spotify-visible device name, but it contributes nothing beyond the schema for device_id or response_format.
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 states a specific verb ('Rename') and resource ('device') and immediately scopes the operation with 'locally (sidecar label)'. This distinguishes it from playback/device-control siblings like switch_device, get_devices, and transfer_playback by establishing that it is a local label change, not a Spotify API operation.
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?
The description implies its use case — renaming a device — and the note that 'Spotify has no rename endpoint' signals this is the only available rename path, which is useful routing context. However, it does not state when not to use it, name alternatives explicitly, or mention prerequisites such as whether the device must first exist in the local sidecar store (e.g., via get_devices or device_sync_state).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.