Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Scene Edit Detection

scene_edit_detection

Detect scene edits in selected clips, then create markers or apply cuts in the active sequence. Adjust sensitivity and optionally include linked audio when cutting.

Instructions

Perform scene edit detection on the selected clips in the active sequence. Defaults to creating markers rather than cutting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoCreate markers (default) or apply cuts to the selected clips
sensitivityNoScene-detection sensitivity (default: MediumSensitivity)
apply_cuts_to_linked_audioNoWhen applying cuts, also cut linked audio (default: false)

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. Changed5 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"
    • 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"
+}
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The description adds meaningful default behavior: 'Defaults to creating markers rather than cutting.' This goes slightly beyond the annotations, which only indicate readOnlyHint=false and destructiveHint=false. However, it does not disclose what happens when ApplyCuts is used, such as clip modification or linked-audio behavior, beyond what the schema already states.

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?

The description is a single sentence that front-loads the core action and then clarifies the default behavior. Every word earns its place, and there is no redundancy with the schema.

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 the high schema coverage, optional parameters with defaults, and the presence of an output schema, the description is mostly adequate. The main gap is the lack of differentiation from the similarly named sibling tools such as 'detect_scene_edits' and 'detect_source_scene_changes'.

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 parameters are already well documented. The description restates the default action in plain language but does not add new semantic detail beyond the schema. This matches the baseline for high schema coverage.

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 uses a specific verb and resource: 'Perform scene edit detection on the selected clips in the active sequence.' It is clear about scope and even notes the default behavior. However, it does not distinguish this tool from the similar sibling 'detect_scene_edits' or 'detect_source_scene_changes', so differentiation is incomplete.

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

Usage Guidelines2/5

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

The description implies the tool operates on selected clips in the active sequence, but gives no explicit guidance about when to choose this tool over alternatives. No exclusions, prerequisites, or sibling comparisons are mentioned, leaving the agent to infer usage 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