Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Export Sequence

export_sequence

Render and export the active sequence with an Adobe Media Encoder preset to a specified output path, with range and overwrite safeguards.

Instructions

Export the active sequence directly (Premiere renders it; blocks until done) with an Adobe Media Encoder preset. The output extension must match what the preset writes (an H.264 preset in AME's QuickTime folder writes .mov); a missing extension is added. Refuses an output_path that already exists unless overwrite is true. Fails if Premiere rejects the render, and verifies a non-empty file was written (for an overwrite, that the file changed). range 'work_area' fails closed unless the work area is enabled and covers only part of the sequence — otherwise Premiere would encode the entire timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoWhat to render: the entire sequence (default), the sequence in/out range (set_sequence_in_out_points), or the work area. work_area requires an enabled work area around part of the sequence; unset or full-sequence work areas are refused instead of encoding everything. Set and read back a valid work area where the host supports it, or use in_to_out for a ranged export.
overwriteNoReplace a file that already exists at output_path (default: false, which refuses the export). The replacement is only reported as written when the file's size or modification time changes.
output_pathYesFull output file path (e.g., '/Users/me/exports/video.mp4')
preset_pathNoPath to an AME preset file (.epr). Uses the default H.264 (MP4) Match Source preset if omitted.
work_area_onlyNoDeprecated alias for range: 'work_area'
timeout_minutesNoHow long to wait for the render (default: 15; long sequences such as full podcast episodes may need more)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.19.0
    • changedInput schema / properties / range / description
      Previous value: -"What to render: the entire sequence (default), the sequence in/out range (set_sequence_in_out_points), or the work area. Scripts cannot set the work area on current Premiere builds, so prefer in_to_out for a ranged export."New value: +"What to render: the entire sequence (default), the sequence in/out range (set_sequence_in_out_points), or the work area. work_area requires an enabled work area around part of the sequence; unset or full-sequence work areas are refused instead of encoding everything. Set and read back a valid work area where the host supports it, or use in_to_out for a ranged export."
  2. Changed7 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / overwrite
      Added value: +{
+  "description": "Replace a file that already exists at output_path (default: false, which refuses the export). The replacement is only reported as written when the file's size or modification time changes.",
+  "type": "boolean"
+}
    • changedInput schema / properties / preset_path / description
      Previous value: -"Path to an AME preset file (.epr). Uses default H.264 if omitted."New value: +"Path to an AME preset file (.epr). Uses the default H.264 (MP4) Match Source preset if omitted."
    • addedInput schema / properties / range
      Added value: +{
+  "description": "What to render: the entire sequence (default), the sequence in/out range (set_sequence_in_out_points), or the work area. Scripts cannot set the work area on current Premiere builds, so prefer in_to_out for a ranged export.",
+  "enum": [
+    "entire",
+    "in_to_out",
+    "work_area"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / timeout_minutes
      Added value: +{
+  "description": "How long to wait for the render (default: 15; long sequences such as full podcast episodes may need more)",
+  "maximum": 240,
+  "minimum": 1,
+  "type": "number"
+}
    • changedInput schema / properties / work_area_only / description
      Previous value: -"Export only the work area (default: false, exports entire sequence)"New value: +"Deprecated alias for range: 'work_area'"
    • 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."
  3. Changed2 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"
    • 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"
+}
  4. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  5. First observedv1.1.1

TDQS

A4.6/5.0
Behavior5/5

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

With annotations only covering the safety profile (readOnly=false, destructive=false, idempotent=false), the description carries the rest: it blocks until the render completes, refuses an existing output_path unless overwrite is true, fails on a Premiere render rejection, and verifies a non-empty (or changed, for overwrite) file was written. Those are the failure and side-effect semantics an agent needs and none are in the annotations.

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?

Front-loaded with the core action and mechanism, then failure/verification behavior. The overwrite and work_area sentences restate the corresponding schema parameter descriptions almost verbatim, which is mild waste, but nothing else is padding.

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?

An output schema and full annotations exist, so return values and safety need not be explained. Combined with the disclosed blocking, extension, overwrite, and verification behavior, the definition is complete enough for a mutation tool of this complexity.

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 coverage is 100%, so the baseline is 3, but the description adds rules the schema does not: the output extension must match what the preset writes, a missing extension is added, and range 'work_area' fails closed rather than silently encoding the whole timeline. The default preset and timeout values duplicate the schema, which caps this at 4.

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 and resource ('Export the active sequence') plus the mechanism ('Premiere renders it; blocks until done'), which cleanly separates it from queue-oriented siblings like add_to_render_queue and from the other exporters (export_aaf, export_frame, export_as_project). An agent can identify the tool without opening the schema.

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

Usage Guidelines4/5

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

Gives clear conditions for the range choice (work_area only when enabled and partial, otherwise in_to_out) and states the blocking contract, which implies when this tool is appropriate. It never names a sibling as the alternative for the queued/non-blocking path, so the routing guidance is implicit rather than explicit.

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