Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

undo_last_mutation

Revert your most recent reversible Spotify change, maintaining operation order. Use the optional dry run to preview exactly what will be undone before applying it.

Instructions

Undo the most recent reversible mutation (receipt FIFO). Same inversion semantics as undo_mutation. Supports dry_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. Addedv1.26.1

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and it does disclose key traits: only reversible mutations are undone, ordering is FIFO by receipt, the inversion semantics match undo_mutation, and dry_run is supported. It does not describe no-op/error behavior, but the main side effects and scope are clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences containing the core operation, ordering semantics, reference semantics, and a preview option. There is no filler, and the most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-optional-param tool the core call is clear, but because there are no annotations and no output schema, the description leaves return behavior and failure/no-op cases unstated and relies on the sibling undo_mutation definition for 'inversion semantics'. The references make it usable, not fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Parameter schema coverage is 100% and both parameters already have meaningful descriptions. The description only restates dry_run support without adding new relationship, precedence, or format details, so it adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Undo'), a precise target ('the most recent reversible mutation'), and an ordering rule ('receipt FIFO'). It also distinguishes itself from sibling undo_mutation by selecting the latest entry rather than a specific one, so an agent knows what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'most recent reversible mutation' implies when this tool applies, and the reference to undo_mutation signals an alternative exists for other undo cases. It does not explicitly say 'use undo_mutation for a specific receipt' or list exclusion cases, so it leaves some routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools