Premiere Pro MCP Server

Scene Edit Detection

scene_edit_detection

Detect scene edits in selected video clips and create segmentation markers or apply cuts at each cut point. Reports detected cuts in source and timeline seconds.

Instructions

Perform Premiere's scene edit detection on the selected clips in the active sequence (it analyses the footage and can take minutes on long clips). CreateMarkers (default) puts Segmentation markers on the selected clips' source project items (shared by every sequence that uses them), removes duplicates this run created (markers that were already there are never deleted), and reports each detected cut in source and timeline seconds; it is verified only when at least one new marker was added. ApplyCuts razors the selected clips and verifies the clip count grew. EXPERIMENTAL QE: CreateMarkers records an observed marker boundary for guarded Undo/Redo; crossing it is refused by default, and unreadable history records unknown protection. This boundary does not verify native marker reversal.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	No	Create markers (default) or apply cuts to the selected clips
`sensitivity`	No	Scene-detection sensitivity (default: MediumSensitivity)
`apply_cuts_to_linked_audio`	No	When applying cuts, also cut linked audio (default: false)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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."

Changed5 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / action

Added value: +{
+  "description": "Create markers (default) or apply cuts to the selected clips",
+  "enum": [
+    "CreateMarkers",
+    "ApplyCuts"
+  ],
+  "type": "string"
+}

addedInput schema / properties / apply_cuts_to_linked_audio

Added value: +{
+  "description": "When applying cuts, also cut linked audio (default: false)",
+  "type": "boolean"
+}

addedInput schema / properties / sensitivity

Added value: +{
+  "description": "Scene-detection sensitivity (default: MediumSensitivity)",
+  "enum": [
+    "LowSensitivity",
+    "MediumSensitivity",
+    "HighSensitivity"
+  ],
+  "type": "string"
+}

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"
+}

First observedv1.1.1May 28, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes far beyond the annotations: warns the analysis can take minutes on long clips, explains that markers land on source project items shared by every sequence using them, that duplicates from this run are removed while pre-existing markers are never deleted, gives explicit verification criteria, and documents the EXPERIMENTAL QE undo/redo boundary behavior including the 'unreadable history records unknown protection' edge case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and the timing caveat before mode details, and each sentence carries distinct information (defaults, dedupe rules, verification, QE caveats). It is dense and slightly long, but very little is filler.

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

Completeness5/5

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

With an output schema present it correctly avoids describing return values, and it still covers the mutation semantics, verification conditions, side effects on shared project items, and the experimental undo-protection behavior. Nothing an agent needs to invoke this safely on a sequence 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 100%, so the schema already documents action, sensitivity, and apply_cuts_to_linked_audio. The description restates the default for action (CreateMarkers) and the semantics of that mode but adds no format or syntax detail for sensitivity or apply_cuts_to_linked_audio, so the baseline 3 applies.

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?

States a concrete verb and resource ('Perform Premiere's scene edit detection on the selected clips in the active sequence') and enumerates both modes (CreateMarkers, ApplyCuts) with their distinct effects. An agent can distinguish this from generic marker or edit tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains what each action does and when verification succeeds, which implies the two use cases, but it never names or contrasts the close siblings detect_scene_edits or detect_source_scene_changes, nor does it state when NOT to use this tool. Usage is implied rather than explicitly guided.

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

Deploy Server