Skip to main content
Glama

Change aspect ratio mid-video

add_aspect_shift

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. CHANGE THE ASPECT RATIO MID-VIDEO, SMOOTHLY — THE tool for 'go vertical for this bit' / 'squeeze to square here and back'. At at_output_s the visible frame MORPHS to ratio over duration_s (0.1-4s, 0.8 default) with an eased close-in, and stays there until the next shift; add another with ratio='source' to open back out. The rendered file keeps ONE resolution — it has to, that is what a video file is — so the change is the frame itself closing in, which is exactly what a smooth aspect change looks like and is why it cannot desync audio or move a caption. zoom=true (default) pushes the picture in as the frame narrows so the subject holds its size. color is the bars' colour. For changing the aspect of the WHOLE video use set_frame or auto_reframe instead. Remove one with remove_aspect_shift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoomNo
colorNo
ratioYes
duration_sNo
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
at_output_sYes
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations are minimal (readOnlyHint false, destructiveHint false), so the description carries the full burden. It discloses the morph mechanism, single-resolution constraint, audio/caption safety, zoom behavior, default duration, and the return of project identity – far beyond annotation coverage.

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?

Dense but well-structured, front-loaded with project scope and core action. Every sentence adds value – no fluff, efficient use of space for the complexity.

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?

Complete for a complex tool: explains behavior, parameters, alternatives, removal, and return value. No output schema, but description covers everything an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers only 29% of parameters (project_id and motion_motif). The description explains at_output_s, ratio, duration_s (with range and default), zoom (default and effect), color, and motion_motif's purpose, comprehensively filling the coverage gap.

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: changes aspect ratio mid-video. Clearly describes the morph effect and distinguishes from whole-video tools (set_frame, auto_reframe) and the removal tool (remove_aspect_shift). The action is unambiguous.

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

Usage Guidelines5/5

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

Explicitly says when to use (mid-video aspect shifts) and names alternatives for whole-video changes and removal. Provides clear routing criteria, leaving no ambiguity about selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.