Premiere Pro MCP Server

Export Sequence Clip Review Frames

export_sequence_clip_review_frames

Exports a file-verified composite frame at the midpoint of each clip on a chosen video track in one bridge request for read-only review, without altering the sequence.

Instructions

Export one file-verified composite frame at the midpoint of each clip on a chosen video track in one bridge request. Read-only in Premiere; it does not mute tracks or claim visual quality.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum clips to sample (default: 20; maximum: 50)
`output_dir`	Yes	Existing directory for clip_001.png and subsequent review frames
`track_index`	No	Zero-based video track index (default: 0)

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.

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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."

Addedv1.14.4Aug 29, 2026

TDQS

B3.1/5.0

Behavior1/5

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

The description says 'Read-only in Premiere' while annotations declare readOnlyHint=false, a direct contradiction. Because the annotations already set a non-read-only profile, the description's opposite claim is misleading rather than additive.

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 the core operation and no obvious padding. The second clause is a defensive caveat whose contradictory read-only claim weakens it, but the structure is otherwise efficient.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Though an output schema and full schema descriptions exist, the description gives a false read-only claim and lacks usage routing among many export siblings. For a tool whose annotations say it is not read-only, this is a significant completeness 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%, so all three parameters are documented in the schema. The description only hints at track selection and per-clip sampling, adding no defaults, limits, or output naming beyond the schema.

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 (Export), resource (one composite frame at midpoint of each clip), and scope (chosen video track, one bridge request). This distinguishes it from sibling export tools that target markers or whole sequences.

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?

Implies use for per-clip review frames by describing the midpoint sampling and chosen track, but never names alternatives such as export_sequence_review_frames or export_frame. The caveat about muting tracks and visual quality is a limitation, not when-to-use guidance.

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

Deploy Server