Compare a Spotify playlist's current state against a stored snapshot to identify added or removed tracks.
Compare current playlist state to a stored snapshot
| Name | Required | Description | Default |
|---|---|---|---|
| playlist_id | Yes | Playlist ID | |
| snapshot_id | Yes | Snapshot ID to compare against | |
| response_format | No | 'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object | concise |
Changes observed during successful MCP inspections.
v1.28.0Input schema / properties / response_formatAdded value: +{
+ "default": "concise",
+ "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+ "enum": [
+ "concise",
+ "detailed",
+ "json"
+ ],
+ "type": "string"
+}v1.26.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, but it only states the operation. It does not disclose whether the tool is read-only, what side effects occur, what error conditions exist (e.g., missing snapshot), or what the returned diff contains.
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 compact phrase with no filler. Every word contributes to the core meaning, and the main action is front-loaded. It is concise but arguably too spare given the lack of annotations and output schema.
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?
Given no output schema, no annotations, and a large set of similarly named snapshot/diff tools, this description is not complete enough. It does not explain what the diff result looks like, how response_format changes the output, or when this tool is preferred over siblings.
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%, so all three parameters (playlist_id, snapshot_id, response_format) are already documented. The description adds no parameter-specific meaning, so the baseline of 3 is appropriate.
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 ('Compare') and the two operands: current playlist state and a stored snapshot. This distinguishes it from snapshot-vs-snapshot tools like diff_playlist_snapshots, but it does not explicitly name or differentiate from sibling tools such as snapshot_diff_summary or find_new_since_snapshot.
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 given for when to use this tool versus alternatives like diff_playlist_snapshots, playlist_diff, or find_new_since_snapshot. It also does not mention prerequisites such as the snapshot needing to exist or what happens if the playlist has no snapshot.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.