Premiere Pro MCP Server

Export Sequence Edl

export_sequence_edl

Generate a CMX 3600 EDL from any video or audio track in a Premiere Pro sequence, self-validate it, and return it inline or save 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.

Input Schema

TableJSON 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).
`include_disabled`	No	Include disabled clips as events (default false).
`record_start_seconds`	No	Record timecode origin in seconds (default: the sequence zero point).
`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

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.1Sep 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations are neutral (readOnlyHint=false, etc.), but the description adds value by clarifying 'Premiere is only read' (no timeline mutation) and 'self-validate it', plus the output path restriction. This goes beyond structured fields, though it does not discuss failure modes or side effects like file overwriting beyond schema constraints.

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 with zero filler. The core purpose is front-loaded, followed by the key behavioral note (read-only, not native) and output options. Every clause earns its place.

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?

Given the 12 parameters fully documented in schema and an output schema present, the description covers the essential behavior: what it exports, how it outputs, and the workspace constraint. It could mention the single-track limitation more explicitly, but that is implied by 'one video or audio track'. Overall it is sufficient for an agent to decide to call it.

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 coverage is 100%, so the baseline is 3. The description mentions 'M2 lines for retimed clips' and 'source/record timecode' as part of the EDL content, but it does not explain any individual parameter beyond what the schema already documents. No additional semantic value is added for the 12 parameters.

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 description states a specific verb and resource: 'Generate a CMX 3600 EDL' for one track of a sequence, with explicit details (cuts, reels, timecode, M2 lines). It also distinguishes itself from siblings like export_as_fcp_xml by naming the format and adding 'this is not a Premiere-native export', making it unmistakable.

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?

It gives clear context: reads from Premiere timeline, not a native export, and can return inline or write to an approved workspace. However, it does not explicitly name alternatives or state when to prefer this over export_as_fcp_xml or import_edl, so it stops short of full exclusion guidance.

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

Deploy Server