Premiere Pro MCP Server

Create Editorial Plan

create_editorial_plan

Read-onlyIdempotent

Creates a local, evidence-backed editorial workflow plan from existing project context to guide organize, stringout, rough cut, caption review, or platform cutdown decisions without altering Premiere.

Instructions

Create a local, evidence-backed editorial workflow plan from captured project context. It never calls an LLM, uploads media, or changes Premiere.

Input Schema

TableJSON Schema

Name	Required	Description
`intent`	Yes	The editorial goal used to retrieve relevant local evidence.
`workflow`	Yes	The workflow to plan. Every workflow remains review-only.
`project_id`	Yes	Project context ID returned by manage_project_context capture.
`sequence_id`	No	Optional exact sequence ID filter for evidence retrieval.
`max_candidates`	No	Maximum evidence candidates to include; defaults to 8.
`platform_targets`	No	Required only for platform_cutdown. These are proposed derivative sequence dimensions; this tool does not create or reframe a sequence.
`organization_rules`	No	Required only for organize. Rules are supplied by the editor or MCP client; the server does not infer categories from filenames alone.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / intent / maxLength
```
Added value: +1000
```
- addedInput schema / properties / intent / minLength
```
Added value: +1
```
- addedInput schema / properties / max_candidates / maximum
```
Added value: +32
```
- addedInput schema / properties / max_candidates / minimum
```
Added value: +1
```
- addedInput schema / properties / max_candidates / type
```
Added value: +"integer"
```
- changedInput schema / properties / organization_rules / items / additionalProperties
```
Previous value: -{}New value: +false
```
- addedInput schema / properties / organization_rules / items / properties / color_index / maximum
```
Added value: +14
```
- addedInput schema / properties / organization_rules / items / properties / color_index / minimum
```
Added value: +0
```
- addedInput schema / properties / organization_rules / items / properties / color_index / type
```
Added value: +"integer"
```
- addedInput schema / properties / organization_rules / items / properties / keywords / items / maxLength
```
Added value: +512
```
- addedInput schema / properties / organization_rules / items / properties / keywords / items / minLength
```
Added value: +1
```
- addedInput schema / properties / organization_rules / items / properties / keywords / maxItems
```
Added value: +64
```
- addedInput schema / properties / organization_rules / items / properties / keywords / minItems
```
Added value: +1
```
- addedInput schema / properties / organization_rules / items / properties / name / maxLength
```
Added value: +255
```
- addedInput schema / properties / organization_rules / items / properties / name / minLength
```
Added value: +1
```
- addedInput schema / properties / organization_rules / maxItems
```
Added value: +16
```
- changedInput schema / properties / platform_targets / items / additionalProperties
```
Previous value: -{}New value: +false
```
- addedInput schema / properties / platform_targets / items / properties / height / maximum
```
Added value: +8192
```
- addedInput schema / properties / platform_targets / items / properties / height / minimum
```
Added value: +16
```
- addedInput schema / properties / platform_targets / items / properties / height / type
```
Added value: +"integer"
```
- addedInput schema / properties / platform_targets / items / properties / name / maxLength
```
Added value: +64
```
- addedInput schema / properties / platform_targets / items / properties / name / minLength
```
Added value: +1
```
- addedInput schema / properties / platform_targets / items / properties / sequence_name / maxLength
```
Added value: +255
```
- addedInput schema / properties / platform_targets / items / properties / sequence_name / minLength
```
Added value: +1
```
- addedInput schema / properties / platform_targets / items / properties / width / maximum
```
Added value: +8192
```
- addedInput schema / properties / platform_targets / items / properties / width / minimum
```
Added value: +16
```
- addedInput schema / properties / platform_targets / items / properties / width / type
```
Added value: +"integer"
```
- addedInput schema / properties / platform_targets / maxItems
```
Added value: +8
```
- addedInput schema / properties / platform_targets / minItems
```
Added value: +1
```
- addedInput schema / properties / project_id / maxLength
```
Added value: +512
```
- addedInput schema / properties / project_id / minLength
```
Added value: +1
```
- addedInput schema / properties / sequence_id / maxLength
```
Added value: +128
```
- addedInput schema / properties / sequence_id / minLength
```
Added value: +1
```

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

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

Addedv1.13.0Aug 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already convey a safe, read-only, idempotent profile. The description adds valuable concrete behavioral guarantees: local execution, no LLM invocation, no media uploads, and no Premiere mutations. This goes beyond the structured annotations and is consistent with them. It does not describe output or persistence behavior, but the output schema and annotations reduce the need for that.

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 two tight sentences with no filler. It front-loads the purpose first, then packs the key behavioral constraints into a compact second sentence. Every clause 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?

Given 100% schema parameter coverage, a rich input schema with conditional requirements, an output schema, and safety annotations, the description is nearly sufficient. The main missing piece is situating the tool among planning-related siblings like preview_editorial_plan and create_editorial_context_pack, which would strengthen tool-selection confidence.

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%, and the schema already explains required parameters, conditionally required nested objects, and defaults. The description reinforces the 'evidence-backed' and 'captured project context' framing for intent/project_id but adds no per-parameter information beyond what the schema provides. Baseline 3 is appropriate given full 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 clearly identifies the action (create), the resource (editorial workflow plan), and the input source (captured project context), with useful qualifiers like 'local' and 'evidence-backed.' It does not explicitly contrast itself with close siblings such as preview_editorial_plan or create_context_edit_plan, so differentiation is implied rather than stated.

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?

The description implies appropriate use: when you have captured project context and need a plan, since it is local and evidence-backed. It also provides useful exclusions ('never calls an LLM, uploads media, or changes Premiere'). However, it does not explicitly name alternatives or state when to use another tool such as preview_editorial_plan, manage_project_context, or create_context_edit_plan.

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

Deploy Server