Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Preview Edit Plan

preview_edit_plan

Preview and validate a planned sequence edit without changing Premiere, returning a single-use token required to apply it.

Instructions

Inspect sequence, project item, clip and requested track targets before previewing a compound timeline edit without changing Premiere. Returns a single-use confirmation token bound to stable project, sequence and target identities; it expires after 30 minutes and is required by apply_edit_plan.

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.

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

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is partly covered. The description adds important behavioral context beyond that: the token is single-use, bound to stable project/sequence/target identities, expires in 30 minutes, and is required by apply_edit_plan. It does not describe validation failure modes, but the output schema can cover return details.

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 tool's scope and non-destructive constraint, followed by the token lifecycle and dependency on apply_edit_plan. Every sentence earns its place.

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 tool with a nested 100-operation plan and an output schema, the description covers purpose, preconditions, and token lifecycle sufficiently. It could mention whether operation ordering or validation errors are surfaced, but given the rich schema and annotations, the definition is largely complete.

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%, including detailed nested descriptions for operations, fields, and defaults. The description only summarizes the affected entities (sequence, project item, clip, track targets) and adds no syntax, constraints, or examples beyond what the schema already provides. Baseline 3 applies when the schema does the heavy lifting.

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 (Inspect), the resources (sequence, project item, clip, requested track targets), and the scope (previewing a compound timeline edit without changing Premiere). It also explicitly distinguishes itself from apply_edit_plan by noting the returned token is required by that tool.

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 clearly establishes when to use the tool: before applying a compound edit and specifically because apply_edit_plan requires the returned token. It does not name any alternative or explicitly state when not to use it, but the sequencing constraint is unambiguous.

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