Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Undo

undo

Reverts recent editing actions in Premiere Pro; use count to specify multiple undo steps. Note: Premiere lacks a supported undo-stack API, so scripted undo cannot be executed or verified.

Instructions

Unavailable: Premiere exposes no supported, observable undo-stack API, so a scripted undo cannot be performed or verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of times to undo (default: 1)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Addedv1.4.0
  3. Removedv1.1.5
  4. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

The annotations only provide generic false hints; the description adds the key behavioral fact that the operation is unsupported and unverifiable because Premiere has no observable undo-stack API. This goes well beyond the schema and tells the agent not to expect a real undo effect.

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?

A single front-loaded sentence states unavailability, provides the reason, and states the consequence. There is no filler, repetition of the schema, or unnecessary detail.

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 stub with an output schema and annotations, the description covers the essential facts: the operation is unsupported and unverifiable. It could be slightly more complete by pointing to an alternative or telling the agent how to respond, but it is sufficient to prevent misuse.

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

Parameters4/5

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

The schema already documents the count parameter with 100% coverage, which sets the baseline at 3. The description adds meaningful global context that makes the count ineffective, since no undo operation can actually be performed.

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

Purpose4/5

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

The description immediately says the tool is unavailable and explains why, so an agent understands this is not a functioning undo operation. It is not a tautology, but it does not differentiate itself from sibling tools such as redo or multiple_undo.

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 opening 'Unavailable' and the statement that a scripted undo 'cannot be performed or verified' provide an explicit when-not: this tool should not be relied on for undo. It stops short of naming an alternative, so it does not reach full routing guidance.

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