Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Apply Edit Plan

apply_edit_plan

Apply a previewed compound edit to a Premiere Pro sequence after revalidating project, sequence, and targets; requires the exact confirmation token. Changed targets need a fresh preview.

Instructions

Apply a previously previewed compound edit after revalidating stable project, sequence and target identities before activation or mutation. Requires the edit capability and exact preview confirmation token; changed targets require a fresh preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYesAn edit plan: { sequence_id?, operations: [...] } with up to 100 insert_clip and remove_clip operations. Operations run in order, and each one's times refer to the timeline as the operations before it left it.
confirmation_tokenYesExact token returned by preview_edit_plan

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / plan / description
      Previous value: -"An edit plan containing insert_clip and remove_clip operations (maximum 100)"New value: +"An edit plan: { sequence_id?, operations: [...] } with up to 100 insert_clip and remove_clip operations. Operations run in order, and each one's times refer to the timeline as the operations before it left it."
    • addedInput schema / properties / plan / properties
      Added value: +{
+  "operations": {
+    "items": {
+      "properties": {
+        "audio_track_index": {
+          "description": "insert_clip: audio track (default 0)",
+          "minimum": 0,
+          "type": "integer"
+        },
+        "include_linked": {
+          "description": "remove_clip without ripple: also remove linked audio/video partners (default true)",
+          "type": "boolean"
+        },
+        "item_id": {
+          "description": "insert_clip: project item node ID or name",
+          "type": "string"
+        },
+        "node_id": {
+          "description": "remove_clip: timeline clip node ID",
+          "type": "string"
+        },
+        "ripple": {
+          "description": "remove_clip: close the gap with a verified sync-locked ripple delete (always takes linked partners)",
+          "type": "boolean"
+        },
+        "start_seconds": {
+          "description": "insert_clip: timeline insert time in seconds (insert edit, sync-locked tracks shift)",
+          "minimum": 0,
+          "type": "number"
+        },
+        "type": {
+          "enum": [
+            "insert_clip",
+            "remove_clip"
+          ],
+          "type": "string"
+        },
+        "video_track_index": {
+          "description": "insert_clip: video track (default 0)",
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "type"
+      ],
+      "type": "object"
+    },
+    "maxItems": 100,
+    "minItems": 1,
+    "type": "array"
+  },
+  "sequence_id": {
+    "description": "Sequence name or ID to edit (activated first); defaults to the active sequence",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / plan / required
      Added value: +[
+  "operations"
+]
    • changedOutput schema / properties / data / description
      Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."
  2. Changed2 schema fields changedv1.14.9
    • removedInput schema / properties / plan / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / plan / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. 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"
+}
  4. Addedv1.4.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, which tells the agent this mutates state but isn't destructive and isn't idempotent. The description adds that it revalidates identities before activation/mutation and requires exact confirmation token. It does not mention what happens if validation fails, nor does it detail the non-destructive nature (e.g., undoable?). With annotations covering safety profile, a 3 is appropriate as the description adds some but not rich behavioral context.

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 sentences, front-loaded with the core action and key requirements. No wasted words; every clause adds necessary context (revalidation, capabilities, token, fresh preview).

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?

Given a nested-object schema with output schema present and annotations covering safety, the description provides sufficient context: it clarifies the preview requirement, the token, and the revalidation step. It could mention the capability requirement more explicitly (it says 'Requires the edit capability') and perhaps what happens on success/failure, but overall it is complete for correct invocation.

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 description coverage is 100%, so the schema already documents all parameters in detail. The description mentions 'exact preview confirmation token' which maps to the confirmation_token parameter but adds no new syntax or format details. Baseline 3 when schema does the heavy lifting.

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 states a specific verb and resource: 'Apply a previously previewed compound edit'. It clearly distinguishes itself from siblings like preview_edit_plan or apply_effect by emphasizing 'compound' and 'previously previewed'. However, it could more explicitly name the sibling preview_edit_plan as the source of the plan.

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 specifies that the plan must be previously previewed and requires a 'exact preview confirmation token', implying preview_edit_plan must be called first. It also states 'changed targets require a fresh preview', giving a condition for when to re-preview. No explicit when-not-to-use guidance, but clear context.

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