premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Export Sequence Edl

export_sequence_edl

Generates a CMX 3600 EDL for one video or audio track from a Premiere sequence, validates it, and returns it inline or writes it to an approved workspace.

Instructions

Generate a CMX 3600 EDL for one video or audio track of a sequence from Premiere timeline readback (cuts, reels, source/record timecode, M2 lines for retimed clips), self-validate it, and return it inline or write it inside an approved workspace. Premiere is only read; this is not a Premiere-native export. Long sequences can use a longer timeout (default 30 minutes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_sequence_edl"
  }
}

Input Schema

Name	Required	Description
`title`	No	TITLE line (default: the sequence name).
`reel_mode`	No	How reel names are derived: clip_name (default), tape_name (XMP tapeName when present), or numbered.
`drop_frame`	No	Write drop-frame timecode (29.97/59.94 only). Defaults to the sequence display format.
`frame_rate`	No	Override the CMX timecode rate; defaults to the sequence rate (23.976 is written as 24).
`track_type`	No	Track type to export (default video).
`output_path`	No	Optional absolute .edl path to write. Requires approved_workspace_path; the file must not already exist. When omitted the EDL text is returned inline.
`sequence_id`	No	Sequence ID or name. Defaults to the active sequence.
`track_index`	No	Track index to export (default 0).
`return_content`	No	Include the per-event list and reel list in the result (default true). With output_path, false returns only the path, event count, record duration, checksum and validation, which keeps long EDLs out of the conversation.
`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 timeline readback (default: 30 minutes).
`include_disabled`	No	Include disabled clips as events (default false).
`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.
`record_start_seconds`	No	Record timecode origin in seconds (default: the sequence zero point).
`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`	No	Absolute existing directory that must contain output_path. Required with output_path.
`include_clip_name_comments`	No	Emit '* FROM CLIP NAME:' comments (default true).

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

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false but say nothing about the read-vs-write split; the description resolves that by clarifying the Premiere project is only read while output goes to disk, and adds that the EDL is self-validated before returning. It does not cover file-overwrite behavior or what validation failure looks like, though the schema partly does (output_path must not already exist).

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 sentences, front-loaded with purpose and followed by scope and safety caveats; nothing is redundant. The heavy parenthetical in the first sentence ('cuts, reels, source/record timecode, M2 lines for retimed clips') slightly slows scanning but each item earns its place as an output-content disclosure.

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?

With 17 parameters, nested CEP guard objects, and an output schema, the description covers what an agent most needs: what gets produced, where it goes, that Premiere is read-only, and that generation can be slow. The detailed idempotency and workspace-guard semantics live in the schema, so leaving them out of the description is reasonable.

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 parameter meaning is already fully documented. The description reinforces track scope and the 30-minute default timeout but adds no syntax, defaults, or interactions beyond what the schema states, so the baseline of 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?

The opening clause names a specific verb, resource, and format: 'Generate a CMX 3600 EDL for one video or audio track of a sequence from Premiere timeline readback.' The explicit CMX 3600 / EDL format and single-track scope separate it cleanly from the other sequence exporters (FCP XML, AAF, OMF) without needing to name them.

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?

It supplies useful context ('Premiere is only read; this is not a Premiere-native export') and a timeout hint for long sequences, and the inline-vs-file choice is implied by output_path. But it never states when an agent should pick this over export_as_fcp_xml, export_aaf, or the inspect/validate_cmx3600_edl siblings, so selection rests on the agent's own format knowledge.

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

Deploy Server