Skip to main content
Glama

undo

Revert the last N actions in DaVinci Resolve via Cmd+Z when the scripting API lacks native rollback; confirm edits with timeline_get.

Instructions

Undo the last N actions by sending Cmd+Z to Resolve (the scripting API has no undo). Needs macOS Accessibility permission. Scripted edits may count as several undo steps — verify with timeline_get.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the macOS Accessibility permission requirement and the non-obvious caveat that one scripted edit may consume several undo steps. Gaps remain around failure behavior and whether undo crosses save boundaries.

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 tight sentences, front-loaded with the action and mechanism, followed by the two operational caveats. Nothing is wasted.

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

Completeness4/5

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

For a one-parameter, no-output-schema tool this is nearly complete: mechanism, permission prerequisite, granularity caveat, and a verification path are all present. Only error and boundary behavior is missing.

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?

Schema coverage is 0%, so the description must compensate for the single 'steps' parameter. It adds real meaning by tying N to actions and warning that steps are not one-to-one with edits, but it leaves the default (1) unstated and does not define behavior when steps exceeds history depth.

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?

The description names a specific verb and scope (undo the last N actions) and explains the mechanism (sending Cmd+Z to Resolve) plus why it exists (the scripting API has no undo). No sibling offers undo, and the mechanism makes the behavior unambiguous.

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?

It makes clear this is the only route to undo, since the API has none, and it directs the agent to verify results with timeline_get. It does not state when not to use it or what happens if steps exceeds available history.

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