Premiere Pro MCP Server

Preview Stacked Camera Edit

preview_stacked_camera_edit

Read-onlyIdempotent

Preview exact enable states for reviewed, pre-razored stacked camera clips while preserving master audio; refuses unreviewed cuts, retiming/nests, or missing lock/link state.

Instructions

Preview exact enable states for pre-razored ordinary stacked camera clips and preserve master audio. Refuses unreviewed cuts, retiming/nests, missing lock/link state. Apply creates a duplicate sequence first; no native multicam switch API is claimed.

Input Schema

Name	Required	Description
`cuts`	Yes	Contiguous reviewed camera ranges.
`snapshot`	Yes	Version 1 canonical snapshot from inspect_timeline_snapshot or an equivalent verified adapter; exact tick strings, host identities, completeness, tracks/clips and SHA256 revision are validated before use.
`camera_track_ids`	Yes	Inspected camera video track IDs.
`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.
`master_audio_track_ids`	Yes	Master audio track IDs, preserved unchanged.

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.

Changed1 schema field changedv1.25.0Oct 24, 2026

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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description earns credit for adding refusal semantics (unreviewed cuts, retiming/nests, missing lock/link state), the master-audio preservation guarantee, and the honest disclaimer that no native multicam switch API is claimed. These are behavioral constraints not present in the structured annotations.

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-loaded with the purpose and scoping constraints, and the second half covers refusals and the apply distinction in very few words. Some sentences are fragment-like ('Refuses unreviewed cuts, retiming/nests, missing lock/link state') and heavy on domain jargon, but there is little wasted text.

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?

An output schema exists, so return values need not be explained, and the schema fully documents the six parameters including the nested expected_cep_target. The description covers the critical behavioral constraints for a preview tool; the only minor gap is the absence of an explicit pointer to the apply sibling.

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 snapshot, cuts, camera_track_ids and master_audio_track_ids are already well documented in the schema. The description adds no parameter-level syntax, tick format, or identity-check detail beyond what the schema provides, making the baseline 3 correct.

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 (Preview) and object (enable states for pre-razored ordinary stacked camera clips) plus the master-audio preservation goal, which separates it from the apply sibling. The jargon 'pre-razored ordinary' and 'stacked camera' is dense, but an agent can still tell this is a dry-run/validation tool rather than a mutation.

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 'Refuses unreviewed cuts, retiming/nests, missing lock/link state' clause gives concrete when-not conditions, and the mention that 'Apply creates a duplicate sequence first' implies this preview should precede that apply. However, it never explicitly names apply_stacked_camera_edit or says 'call this before applying', so the routing is left to inference.

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

Deploy Server