Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Edit Plan

preview_edit_plan

Validate and preview compound timeline edits before applying them, returning a confirmation token required to execute the edit plan.

Instructions

Validate and preview a compound timeline edit without changing Premiere. Returns a confirmation token required by apply_edit_plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYesAn edit plan containing insert_clip and remove_clip operations (maximum 100)

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.9
    • removedInput schema / properties / plan / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / plan / propertyNames
      Removed value: -{
-  "type": "string"
-}
  2. 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"
+}
  3. Addedv1.4.0

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it guarantees no Premiere mutation, performs validation, and returns a token needed downstream. It does not detail validation failure modes, side effects outside Premiere, or token expiration, but the 'without changing Premiere' statement is a valuable safety disclosure that the annotations alone do not convey.

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 concise sentences, both information-dense. The first front-loads the action and the non-destructive guarantee; the second connects to the required next step. No filler or redundant restatement of the tool name.

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?

The tool is moderately complex due to a nested plan object, but the output schema exists and the single parameter is fully documented. The description covers purpose, safety, and workflow linkage. A small gap is the lack of detail about validation behavior or error conditions, but this is minor given the available schema and output schema.

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 100%: the schema already documents the single 'plan' parameter as an object containing insert_clip and remove_clip operations with a maximum of 100. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Validate and preview') with a concrete resource ('a compound timeline edit'), and explicitly states the key non-mutation guarantee ('without changing Premiere'). It also clearly differentiates itself from apply_edit_plan by naming the confirmation token requirement, so an agent can distinguish this preview step from the actual application step.

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 description clearly implies the usage workflow: call this before apply_edit_plan, since it 'Returns a confirmation token required by apply_edit_plan.' It does not explicitly enumerate alternatives or when-not-to-use scenarios, but the token dependency and visible sibling apply_edit_plan provide strong contextual routing.

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