premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Export Omf

export_omf

Exports the active Premiere Pro sequence as an OMF file for audio post-production, with configurable audio format, sample rate, handles, and timeout handling for long sequences.

Instructions

Export the active sequence as an OMF file (Open Media Framework, for audio post-production). Long sequences can use a longer wait (default 60 minutes); if Premiere writes the file but times out, the receipt includes its size as committed_unverified.

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_omf"
  }
}

Input Schema

Name	Required	Description
`include_pan`	No	Include pan information in the OMF (default: false)
`output_path`	Yes	Full output file path (e.g., '/Users/me/export.omf')
`sample_rate`	No	Audio sample rate (default: 48000)
`handle_frames`	No	Handle length in frames when trimming (default: 1000)
`bits_per_sample`	No	Audio bit depth (default: 16)
`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.
`timeout_minutes`	No	Maximum wait for Premiere to write the OMF (default: 60 minutes for long sequences).
`trim_audio_files`	No	Trim audio to used range plus handles (default: true)
`audio_file_format`	No	Audio format: 0=AIFF, 1=WAV. Default: 1
`audio_encapsulated`	No	Embed audio in OMF (true) or reference external files (false). Default: true
`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=false and destructiveHint=false, so the mutation profile is covered structurally. The description adds genuinely new behavioral context beyond that: the timeout is a wait bound rather than a cancel, and if Premiere writes the file but the call times out the receipt reports committed_unverified with the file size, which tells the agent how to interpret a partial outcome. It does not discuss overwriting an existing file or where the file lands beyond output_path.

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 load-bearing, with the core action stated first and the timeout/partial-failure caveat second. There is no filler or repetition of schema content beyond the necessary timeout reference.

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?

The tool is complex (12 params, nested identity guards, an output schema), but the schema and annotations carry most of that burden and the description supplies the one non-obvious operational fact — the timeout/committed_unverified outcome. A brief note on why a caller would pick OMF over the sibling AAF/EDL exports is the only meaningful gap.

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 all 12 parameters, including the nested expected_cep_target guard and the idempotency_key contract, are documented in the schema itself. The description only restates the timeout default already in the schema, so the baseline of 3 is appropriate.

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 gives a specific verb and resource ('Export the active sequence as an OMF file') and even glosses OMF as Open Media Framework for audio post-production, so the agent knows exactly what is produced. It stops short of explicitly contrasting with siblings like export_aaf or export_sequence_edl, so differentiation is inferred from the format name rather than stated.

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: 'for audio post-production' hints at the scenario, and the mention of long sequences needing a longer wait gives a situational cue for timeout_minutes. There is no explicit when-to-use / when-not-to-use guidance and no named alternative (e.g., AAF or EDL export) against which to choose.

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

Deploy Server