Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

export_omf

Export the active sequence as an OMF file for audio post-production, with configurable sample rate, bit depth, and embedded or referenced audio.

Instructions

Export the active sequence as an OMF file (Open Media Framework, for audio post-production)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesFull output file path (e.g., '/Users/me/export.omf')
sample_rateNoAudio sample rate (default: 48000)
bits_per_sampleNoAudio bit depth (default: 16)
audio_encapsulatedNoEmbed audio in OMF (true) or reference external files (false). Default: true
audio_file_formatNoAudio format: 0=AIFF, 1=WAV. Default: 1
trim_audio_filesNoTrim audio to used range plus handles (default: true)
handle_framesNoHandle length in frames when trimming (default: 1000)
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It does not disclose behavioral traits such as file overwrite behavior, permissions needed, or potential side effects.

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?

The description is a single, front-loaded sentence with no unnecessary words. It efficiently communicates the core purpose.

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?

Despite having 7 parameters and no output schema, the description provides minimal context. It does not explain the export process, success indicators, or typical usage scenarios, leaving the agent underinformed.

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 parameters are well-documented in the schema. The tool description adds no additional meaning beyond what the schema provides, meeting the baseline.

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 clearly states the tool exports the active sequence as an OMF file, specifying the format (Open Media Framework) and its context (audio post-production). It distinguishes itself from sibling export tools like export_aaf or export_sequence.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like export_aaf, or any prerequisites or limitations. The description lacks context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leancoderkavy/premiere-pro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server