Skip to main content
Glama

Reframe Aspect Ratio

reframe
Destructive

Change a source video's aspect ratio to 16:9, 9:16, 1:1, or 4:5 by padding to preserve the full frame or cropping to fill the target.

Instructions

Re-aspect a video to 16:9, 9:16, 1:1, or 4:5 by padding or cropping.

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": {
      "input": "<input>",
      "aspect": "<aspect>"
    },
    "name": "reframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNopad (default): letterbox, nothing lost. crop: fill and center-crop.
inputYesPath to the source video.
aspectYesTarget aspect ratio.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.47.0
    • changedInput schema / properties / fit / description
      Previous value: -"pad (default): scale to fit and letterbox, no content lost. crop: scale to fill and center-crop."New value: +"pad (default): letterbox, nothing lost. crop: fill and center-crop."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds that the operation works by padding or cropping, which hints crop discards picture content, but it does not mention the file-overwrite behavior or default output location that a destructive write tool would benefit from stating.

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?

A single tight sentence with the key constraint (supported ratios) front-loaded and zero filler.

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 a full output schema and fully documented parameters, the description needs only to convey the core effect, which it does. It stops slightly short for a destructive write tool by not noting that output files may be replaced.

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 five parameters including the fit and aspect enums are already documented in detail. The description only restates the aspect enum and the pad/crop choice without adding new semantics, so the baseline 3 applies.

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?

States a specific verb ('Re-aspect') plus resource ('video'), and enumerates the four supported target ratios, which makes it easy to distinguish from neighboring tools. It does not differentiate itself from crop or scale, which also change framing dimensions.

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: an agent can infer it should be called when a video needs a different aspect ratio. There is no explicit guidance on when to prefer this over crop, scale, or export_preset, despite those siblings overlapping in function.

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