premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Create Editorial Plan

create_editorial_plan

Read-onlyIdempotent

Build a local, review-only editorial workflow plan from captured project context and an intent, with evidence-backed candidates for organizing, stringouts, rough cuts, captions, or platform cutdowns—no LLM calls or Premiere changes.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "workflow": "<workflow>",
      "intent": "<intent>"
    },
    "name": "create_editorial_plan"
  }
}

Input 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.
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`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.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output 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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.30.0Nov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false; the description reinforces and extends this by naming three concrete non-actions ('never calls an LLM, uploads media, or changes Premiere'), which tells the agent the tool is offline and side-effect-free on the host. It leaves one thing unstated: whether the 'local' plan is persisted to disk despite the read-only hint.

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, both front-loaded: what it produces first, then the safety envelope. Nothing is repeated from the schema and every clause carries information.

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 10-parameter, nested-schema tool with an output schema, the definition gives a clear purpose and behavioral envelope while correctly delegating parameter detail to the schema. The remaining gap is workflow-level: it does not mention that platform_cutdown and organize impose required structured inputs, though the schema does.

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 prose for idempotency_key and the conditional platform_targets/organization_rules fields, so the schema carries parameter meaning completely. The description adds no parameter-level detail beyond the generic 'captured project context' framing, so the baseline 3 applies.

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?

States a specific verb and artifact ('Create a local, evidence-backed editorial workflow plan') plus the source of truth ('captured project context'), which is far more informative than the title alone. It stops short of distinguishing itself from close siblings such as preview_editorial_plan or create_context_edit_plan, so an agent must infer the boundary.

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?

Usage is only implied: 'from captured project context' hints that a prior manage_project_context capture is required, and the schema's project_id text makes that explicit. There is no statement of when to choose this over preview_editorial_plan or the many plan_* siblings, and no exclusions.

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

Deploy Server