Premiere Pro MCP Server

Plan Audio Post Turnover

plan_audio_post_turnover

Read-onlyIdempotent

Preview a bounded AAF/OMF audio-post turnover contract with exact range, handles, rational rate, channels, gain automation, media hashes, and reference picture, and route to native exporters.

Instructions

Preview a bounded AAF/OMF audio-post turnover contract: exact exclusive range, handles, rational rate, channels, requested gain automation, media hashes and reference picture. Routes to existing native exporters. Caller manifests and exporter settings are not DAW acceptance or audible-alignment proof.

Input Schema

Name	Required	Description
`rate`	Yes	Exact rational frames per second; e.g. 30000/1001.
`media`	Yes	Reviewed media manifest; fields remain caller evidence until file readback.
`range`	Yes	Requested exclusive timeline range
`format`	Yes	Existing native Premiere interchange exporter to review.
`sample_rate`	Yes	Requested audio-post sample rate.
`sequence_id`	Yes	Exact reviewed sequence identity.
`handle_frames`	Yes	Requested media handles in sequence frames; verify source availability separately.
`channel_mapping`	Yes	Reviewed per-track channel mapping, which may require rendering unsupported host layouts.
`gain_automation`	Yes	Declare requested gain handling and retain unsupported state.
`reference_picture`	No	Optional reviewed reference-picture artifact ID/filename; verify its conformance separately.
`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.

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

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is lower, but the description still adds real value: it discloses that it only routes to existing native exporters and, importantly, that caller manifests and exporter settings are not DAW acceptance or audible-alignment proof — a meaningful caveat about the limits of the result.

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?

Two dense sentences, front-loaded with the core action and scope, followed by a caveat. Every clause carries information, though the jargon-heavy phrasing and the slightly ambiguous 'routes to existing native exporters' could be tightened.

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 12-param, 9-required planning tool with a rich output schema and full annotation coverage, the description sets purpose and limits adequately. The one gap is the mild ambiguity around whether 'routes to existing native exporters' implies execution, given readOnlyHint=true.

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 nested objects (rate, range, media, channel_mapping) are fully documented in the schema. The description lists the categories the contract covers but adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Preview/plan) and concrete resource (bounded AAF/OMF audio-post turnover contract), then enumerates the scope it covers: range, handles, rational rate, channels, gain automation, media hashes, reference picture. 'Routes to existing native exporters' distinguishes it from the execute siblings (export_aaf, export_omf) without needing to open a schema.

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 word 'Preview' plus 'Routes to existing native exporters' implies this is a planning step preceding an actual export, but the description never states when to use it versus export_aaf/export_omf, nor any explicit 'do not use for actual export' exclusion. Usage is inferable rather than stated.

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

Deploy Server