premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Export Aaf

export_aaf

Export an AAF file from a Premiere Pro sequence for interchange with other editing tools; CEP backend is unsupported—use the authenticated UXP bridge.

Instructions

Unavailable on the CEP backend. Use export_aaf_uxp with an authenticated Premiere 26.3+ UXP bridge.

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": {
      "output_path": "<output_path>"
    },
    "name": "export_aaf"
  }
}

Input Schema

Name	Required	Description
`output_path`	Yes	Full output file path (e.g., '/Users/me/export.aaf')
`sample_rate`	No	Audio sample rate (default: 48000)
`mix_down_video`	No	Mix down video to single track (default: true)
`bits_per_sample`	No	Audio bit depth (default: 16)
`explode_to_mono`	No	Explode multichannel audio to mono (default: false)
`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.
`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

B3.4/5.0

Behavior3/5

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

The annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) imply a normal working write operation, while the description discloses that the tool is unusable on the CEP backend — valuable context the annotations do not carry. However, it does not say what actually happens when invoked (guaranteed error, error code, whether the large idempotency/expected_cep_target schema is still validated).

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 short sentences, zero filler, and the disqualifying fact ('Unavailable on the CEP backend') is front-loaded ahead of the redirect. Nothing is redundant or buried.

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?

For a disabled stub with a rich 8-parameter schema and an output schema, the description covers the essential decision (don't call it, call the UXP sibling instead) but leaves ambiguity about whether the tool ever works on another backend and what invoking it returns. Enough to avoid a wrong call, not enough to fully characterize behavior.

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 8 parameters (including idempotency_key and expected_cep_target) are thoroughly documented in the schema itself. The description adds no parameter-level meaning, which is acceptable given the schema does the work, but nothing is contributed beyond baseline.

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

Purpose3/5

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

The description never states positively what the tool does (export an AAF); that is only inferable from the name 'export_aaf' and from 'Unavailable on the CEP backend'. It does clearly communicate the tool's status and route, but purpose is implied rather than stated with a verb+resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent not to use this tool and names the replacement (export_aaf_uxp), plus a concrete prerequisite (authenticated Premiere 26.3+ UXP bridge). It stops short of a 5 because it does not say under what conditions, if any, this CEP variant would be the right call.

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

Deploy Server