Premiere Pro MCP Server

Auto Reframe Sequence

auto_reframe_sequence

Reframe a sequence to a target width and height by creating a new auto-reframed sequence and verifying the frame size for the new aspect ratio.

Instructions

Auto-reframe a sequence into a new sequence of target_width x target_height. Premiere derives the new sequence from the source height (a 1080p source at 9:16 comes out 607x1080), so the tool then sets the requested frame size and verifies it; the Auto Reframe effect refits to the new size.

Input Schema

TableJSON Schema

Name	Required	Description
`new_name`	No	Name for the newly created auto-reframed sequence
`sequence_id`	No	Sequence name or ID to reframe. Uses active sequence if omitted.
`target_width`	Yes	Target frame width in pixels
`motion_preset`	No	Premiere Auto Reframe motion preset (default: default)
`target_height`	Yes	Target frame height in pixels
`use_nested_sequences`	No	Whether Auto Reframe should honor nested sequences (default: false)

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

Changed5 schema fields changedv1.14.4Aug 29, 2026

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 / motion_preset

Added value: +{
+  "description": "Premiere Auto Reframe motion preset (default: default)",
+  "enum": [
+    "slower",
+    "default",
+    "faster"
+  ],
+  "type": "string"
+}

addedInput schema / properties / new_name

Added value: +{
+  "description": "Name for the newly created auto-reframed sequence",
+  "type": "string"
+}

addedInput schema / properties / use_nested_sequences

Added value: +{
+  "description": "Whether Auto Reframe should honor nested sequences (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"
+}

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, but the description adds real behavior the annotations cannot: it creates a NEW sequence, Premiere derives dimensions from source height, the tool then forces the requested frame size and verifies it, and the Auto Reframe effect refits afterward. This is useful operational context beyond the flags.

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 action and its output shape, with no filler. The second sentence is dense but every clause carries information about the tool's internal behavior.

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?

With an output schema present, return values need no explanation, and the description covers the creation semantics, the dimension quirk, and verification. It omits any mention of when to prefer this over simpler resize tools, which would round it out.

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 genuine semantics for target_width/target_height by explaining Premiere's derived-sizing behavior (1080p at 9:16 yields 607x1080) before the requested size is applied.

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 ('Auto-reframe a sequence into a new sequence of target_width x target_height'), and the phrase 'into a new sequence' distinguishes it from resolution-mutating siblings like set_sequence_resolution or set_scale_to_frame_size.

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?

Usage is only implied: no explicit when-to-use, when-not, or named alternative is given. An agent can infer this is for reframing (e.g., to vertical) but must decide on its own versus set_sequence_resolution or set_scale_to_frame_size.

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

Deploy Server