Premiere Pro MCP Server

Validate Project For Export

validate_project_for_export

Read-onlyIdempotent

Run a non-mutating export preflight to detect blocking offline media, empty timelines, inaccessible preset/output paths, and timeline gaps before exporting.

Instructions

Run a non-mutating export preflight for an active or named sequence. It reports blocking offline media, empty timelines, inaccessible preset/output paths, duration, and optional timeline gaps without queuing an export. readyForExport means these preflight checks passed; it does not test exporter initialization, encoder availability, or whether the host can render. Require an actual output file from export_sequence and verify_delivery_file before claiming delivery.

Input Schema

TableJSON Schema

Name	Required	Description
`check_gaps`	No	Report gaps on populated tracks as warnings (defaults to true).
`output_path`	No	Optional intended delivery path; its parent folder is checked.
`preset_path`	No	Optional .epr preset path to check.
`sequence_id`	No	Sequence ID or name. Defaults to the active sequence.
`require_non_empty_timeline`	No	Treat an empty sequence as a blocking error (defaults to 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.

Changed1 schema field changedv1.18.6Sep 30, 2026

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed7 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / output_path / maxLength
```
Added value: +4096
```
- addedInput schema / properties / output_path / minLength
```
Added value: +1
```
- addedInput schema / properties / preset_path / maxLength
```
Added value: +4096
```
- addedInput schema / properties / preset_path / minLength
```
Added value: +1
```
- addedInput schema / properties / sequence_id / maxLength
```
Added value: +512
```
- addedInput schema / properties / sequence_id / minLength
```
Added value: +1
```
Addedv1.14.4Aug 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: it defines what readyForExport actually means and explicitly bounds that guarantee, preventing an agent from over-claiming success. This is exactly the kind of behavioral nuance the structured fields cannot convey.

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?

Three sentences, front-loaded with the purpose and tightly packed with the guarantee boundary. It is dense rather than padded, though the limitation clauses make it longer than strictly minimal for a preflight tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be explained, and the description instead covers the semantically critical part — the meaning and limits of readyForExport — plus the required downstream verification. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still adds semantic framing by enumerating what each optional input checks (gaps, empty timelines, preset/output paths, duration), connecting the booleans and paths to observable preflight outcomes rather than restating types.

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 opens with a specific verb and resource: 'Run a non-mutating export preflight for an active or named sequence.' It scopes exactly what it checks (offline media, empty timelines, preset/output paths, duration, gaps) and distinguishes itself from the sibling export_sequence and verify_delivery_file tools by name.

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

Usage Guidelines5/5

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

It states both when to use it (preflight before export) and, more valuably, when it is NOT sufficient: 'it does not test exporter initialization, encoder availability, or whether the host can render.' It names the follow-up tools (export_sequence, verify_delivery_file) required before claiming delivery, which is explicit alternative routing.

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

Deploy Server