Premiere Pro MCP Server

Auto Reframe Sequence

auto_reframe_sequence

Change a video sequence to a new aspect ratio by specifying target width and height. Creates a reframed sequence with optional motion preset and nested sequence handling.

Instructions

Auto-reframe a sequence for a different aspect ratio

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.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

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

C2.9/5.0

Behavior2/5

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

The description adds little beyond the title and does not disclose key behaviors such as whether a new sequence is created, whether the original sequence is modified, or that Auto Reframe performs analysis. Annotations are present but only provide generic false hints; the description does not enrich them.

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?

The description is a single, front-loaded sentence with no filler. It is appropriately concise, though it could use the saved space to mention side effects or creation behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema covers parameters and an output schema exists, so an agent can likely invoke the tool correctly. However, the description omits important contextual information such as whether a new sequence is created and what happens to the original sequence, making it only minimally viable.

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 six parameters are documented. The description only loosely contextualizes the target dimensions as an aspect-ratio change, which adds minimal meaning beyond the schema's explicit parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action ('Auto-reframe'), a resource ('a sequence'), and the purpose ('for a different aspect ratio'). It is clear on its own, but it does not explicitly differentiate from similar sequence-creation or sequence-modification siblings such as create_sequence or set_sequence_resolution.

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?

There is no guidance about when to use this tool versus alternatives, and no mention of prerequisites or situations where another tool would be more appropriate. The intended use is only implied by the action described.

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

Deploy Server