Osiris Premiere MCP

Overview Schema Source Related Servers Discussions Admin

Export Sequence Edl

export_sequence_edl

Generate a CMX 3600 EDL for one video or audio track from Premiere timeline readback, validate it, and return it inline or write 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; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.19.1Oct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes beyond annotations by disclosing that Premiere is only read, that the EDL is self-validated, that writing requires an approved workspace and a non-existent target file, and that output can be inline. Annotations already cover safety profile (readOnly=false, destructive=false, idempotent=false), so this added operational context is meaningful without contradiction.

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?

A single front-loaded sentence packs the artifact, scope, source, and constraints with no filler. It is dense (nested parentheticals) rather than wasteful, though it could be split for readability.

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 an output schema present, return-value detail is unnecessary, and annotations cover the safety profile. The description supplies the read-only Premiere constraint, self-validation, and output-path prerequisites, which is enough for an agent to call it correctly.

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% across all 12 parameters, so the schema already documents title, reel_mode, drop_frame, frame_rate, track_type, output_path, etc. The description adds only the inline-vs-write duality and the M2/retime context, not per-parameter semantics. Baseline 3 is appropriate.

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 (Generate), a specific artifact (CMX 3600 EDL), and a precise scope (one video or audio track of a sequence, from Premiere timeline readback). This clearly separates it from siblings like export_sequence, inspect_cmx3600_edl, and validate_cmx3600_edl.

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 description implies context ('from Premiere timeline readback', 'not a Premiere-native export') and covers the two output modes, but never explicitly says when to choose this over export_sequence, export_as_fcp_xml, or export_aaf, nor when not to use it. Usage is inferable but not stated.

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

Deploy Server