Skip to main content
Glama

auto_reframe_sequence

Reframes the active Premiere Pro sequence to a new aspect ratio using AI-powered motion tracking, so you can adapt edits for vertical, square, or widescreen delivery.

Instructions

Auto-reframe the active sequence to a new aspect ratio (AI-powered reframing)

Input Schema

NameRequiredDescriptionDefault
newNameNoName for the reframed sequence
numeratorYesTarget aspect ratio numerator (e.g. 9 for 9:16 vertical)
denominatorYesTarget aspect ratio denominator (e.g. 16 for 9:16 vertical)
motionPresetNoMotion tracking speed preset (default: 'default')
useNestedSequencesNoWhether to use nested sequences (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions AI-powered reframing and the active sequence context, but does not state whether the original sequence is modified or a new sequence is created, what permissions are needed, or whether the operation is reversible.

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, front-loaded sentence that states the core action and target without any extraneous information. It is appropriately sized for a tool whose parameters are fully documented in the schema.

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

Completeness2/5

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

With no annotations and no output schema, the description should clarify key behavioral details for a potentially significant operation. It does not explain whether a new sequence is created, what happens to the active sequence, or what the result of the operation is, leaving important context gaps.

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?

The schema has 100% description coverage, so all parameters including numerator, denominator, newName, motionPreset, and useNestedSequences are already documented. The description adds only the high-level concept of a target aspect ratio and does not provide additional parameter semantics beyond 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 clearly states a specific verb ('Auto-reframe') and resource ('the active sequence') with the target ('new aspect ratio'). It distinguishes itself from general sequence settings tools by specifying AI-powered reframing, though it does not explicitly differentiate from closely related sequence operations like set_sequence_settings.

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?

The description implies the tool operates on the active sequence but provides no explicit guidance on when to use it versus alternatives, prerequisites such as having an active sequence, or conditions where it should not be used. No sibling tools are named as alternatives.

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