Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export Omf

export_omf

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

Instructions

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_pan
      Added value: +{
+  "description": "Include pan information in the OMF (default: false)",
+  "type": "boolean"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate this is not read-only, not idempotent, and not destructive, so the bar for additional behavioral disclosure is lower. The description adds the target scope ('active sequence') and format, but does not disclose side effects such as file creation/overwriting, whether the OMF embeds or references media, or what happens if no sequence is active. No contradiction with annotations exists.

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, well-structured sentence that front-loads the verb and target, then adds the format clarification. Every word earns its place, with no filler or repetition of schema content.

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?

Given the 100% schema coverage, presence of an output schema, and annotations covering the basic operation type, the description is largely complete for invocation. It could add a hint about prerequisites like requiring an active sequence or note about file overwrite behavior, but these are relatively minor gaps for an export tool whose parameters are fully documented.

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 eight parameters are already documented in the input schema with meaningful descriptions. The tool description itself adds no parameter-level detail, so the baseline score of 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?

The description clearly states a specific verb ('Export'), a specific resource ('the active sequence'), and a specific output format ('OMF file'). The parenthetical '(Open Media Framework, for audio post-production)' further disambiguates the tool from other export tools like export_aaf or export_as_fcp_xml.

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 provides useful context ('for audio post-production') that implies when OMF export is appropriate, but it does not explicitly state when to choose this tool over alternatives such as export_aaf or export_sequence. There is no when-not-to-use guidance or mention of sibling tools.

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

Deploy Server

Other Tools