Premiere Pro MCP Server

Build Project Handoff Manifest

build_project_handoff_manifest

Read-onlyIdempotent

Builds a handoff manifest that reports observed bytes, missing files, expected source identity and unresolved nested dependencies, so a copied project alone cannot pass completeness.

Instructions

Inspect explicitly listed dependencies inside an approved consolidated workspace. Reports observed bytes, missing files, expected source identity and unresolved nests/image sequences/AE/template dependencies. A copied project alone cannot pass completeness.

Input Schema

Name	Required	Description
`dependencies`	Yes	Expected dependencies, at most500.
`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 one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`inventory_complete`	Yes	Whether upstream dependency enumeration is complete, including nested/external sources.
`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.
`approved_workspace_path`	Yes	Existing absolute approved root; symlink escapes reject.

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.

Changed2 schema fields changedv1.25.0Oct 24, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "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 one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}

addedOutput schema / properties / idempotency

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
+  "type": "object"
+}

Addedv1.24.0Oct 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true and openWorldHint=false, and the description usefully resolves the ambiguity of the verb 'build' by making clear this is an inspection that reports findings (observed bytes, missing files, unresolved nested/precomp dependencies) rather than writes an artifact. It also discloses a meaningful policy: completeness cannot be satisfied by a copied project alone. It stops short of saying whether missing files abort the call or are returned in the report, and says nothing about permissions on the approved workspace.

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?

Three short sentences, front-loaded with the action and scope, with zero boilerplate. The closing sentence ('A copied project alone cannot pass completeness') is compact but slightly cryptic in isolation, costing a point of crispness.

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

Completeness3/5

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

With an output schema present, return values need no explanation, and the 100%-covered input schema carries the guard and idempotency detail. Still, for a 6-parameter tool with nested objects sitting in a consolidation-to-handoff workflow, the description never states the ordering prerequisite (a completed consolidation and a complete upstream enumeration) or how inventory_complete=false is treated, leaving an agent to reconstruct the workflow from schema prose.

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 schema already documents approved_workspace_path, dependencies, inventory_complete, and the CEP/idempotency guards in depth; baseline is 3. The description reinforces two of them ('explicitly listed dependencies', 'approved consolidated workspace') but adds no semantics for inventory_complete or the expected_cep_target/expected_project_path guards beyond what the schema states.

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 names a specific action and resource: inspect an explicitly listed dependency set inside an approved consolidated workspace and report observed bytes, missing files, expected source identity, and unresolved nests/image sequences/AE/template deps. That is far more precise than the name alone (which misleadingly suggests producing an artifact). It does not, however, distinguish itself from adjacent audit-style siblings such as inspect_edit_readiness, validate_project_for_export, or consolidate_and_transfer.

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 implied rather than stated: the workspace must be 'approved' and 'consolidated', and the closing line warns 'a copied project alone cannot pass completeness', which hints at a when-not condition. There is no explicit 'use this when…' clause and no sibling is named as the alternative for simple integrity checks, so the agent must infer placement in the handoff workflow.

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

Deploy Server