Export or render the active Premiere Pro sequence directly to a file using an AME preset; synchronous operation blocks Premiere until rendering finishes, so use it for short sequences.
Export/render the active sequence directly (synchronous, blocks Premiere until done - use for short sequences)
| Name | Required | Description | Default |
|---|---|---|---|
| outputPath | Yes | Full output file path | |
| presetPath | Yes | Path to an AME preset file (.epr) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose the key trait: the call is synchronous and blocks Premiere until completion. It says nothing about overwriting an existing output file, behavior on failure, permission requirements, or what is returned, so meaningful gaps remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the operation, the target, and the blocking caveat; no filler and nothing redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The blocking nature and target sequence are covered, which is the core need for a two-parameter export. With no annotations and no output schema, the description should still say whether it overwrites an existing file and what a successful result looks like.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the exported sequence is the *active* one, so no sequence identifier is expected. It adds nothing about outputPath/presetPath beyond the schema, which already documents both.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (export/render) and resource (the active sequence), with 'directly' signaling the synchronous variant. It does not name the sibling export_sequence or explain how the two differ, so the agent must infer the distinction from the parenthetical.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'use for short sequences' is an explicit when-to-use condition, which is better than nothing. However, it never names the alternative tool (export_sequence) or states the when-not case for long sequences, leaving the agent to guess which export path to choose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.