premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Auto Reframe Sequence

auto_reframe_sequence

Creates an auto-reframed sequence at a target width and height, then sets and verifies the frame size so the Auto Reframe effect refits correctly.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_width": "<target_width>",
      "target_height": "<target_height>"
    },
    "name": "auto_reframe_sequence"
  }
}

Input 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
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`use_nested_sequences`	No	Whether Auto Reframe should honor nested sequences (default: false)
`expected_project_path`	No	Optional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output 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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.30.0Nov 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent), the description discloses real behavior: the source sequence is preserved and a NEW sequence is produced, Premiere derives an intermediate size from the source height rather than the requested width, and the tool then sets and verifies the requested frame size before the effect refits. That two-phase derive-set-verify cycle is exactly the kind of non-obvious trait an agent benefits from. It omits how long the Auto Reframe analysis takes or that the operation may block, which keeps it below a 5.

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 result, and the parenthetical example (1080p at 9:16 gives 607x1080) earns its place by making the otherwise opaque derivation rule concrete. The second clause ('so the tool then sets the requested frame size and verifies it') is slightly dense on first read but carries necessary behavioral information.

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 and all nine parameters described in the schema, the description only needs to explain the core transformation and its non-obvious mechanics, which it does. The heavy guard parameters (expected_cep_target, expected_project_path, idempotency_key) are fully documented in the schema, so their absence from the description is acceptable, though a note that the call performs a render-scale analysis would round it out.

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 the baseline is 3. The description does add genuine meaning for target_width/target_height by explaining that Premiere first derives a sequence from source height and the requested size is applied afterwards, which reframes how an agent should think about those two numbers. It says nothing about motion_preset, use_nested_sequences, new_name, or the guard parameters, leaving most of the nine parameters to the schema.

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 verb (auto-reframe) and resource (a sequence), and states the concrete outcome: a new sequence at target_width x target_height. It is distinguishable from sequence-creation siblings because the reframing is explicit. It stops short of naming an alternative tool such as plan_active_speaker_reframe, so it is clear but not sibling-differentiated.

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 implied by 'Auto-reframe a sequence into a new sequence' - an agent can infer this is the tool for changing aspect ratio of an existing sequence. But there is no explicit when-to-use/when-not-to-use guidance, no mention of what to do if the source is already at the target size, and no pointer to any alternative reframing path.

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

Deploy Server