Skip to main content
Glama

Scale Video

scale
Destructive

Resize a video to a target width and/or height, then re-encode it. Set one dimension to keep aspect ratio or both for exact dimensions.

Instructions

Resize a video to a target width and/or height and re-encode. Provide one side to keep the aspect ratio, or both to set an exact 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": {
      "input": "<input>"
    },
    "name": "scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesPath to the source video.
widthNoTarget width in px. Omit to derive from height (keeps aspect).
heightNoTarget height in px. Omit to derive from width (keeps aspect).
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. Changed1 schema field changedv0.47.0
    • 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, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds the meaningful behavioral note that the video is re-encoded, hinting at quality/processing cost, but it does not discuss overwrite risk, encoding defaults, or what happens when the output path already exists.

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?

Two tight sentences with zero filler; the core operation is front-loaded and the aspect-ratio rule follows immediately. Every clause earns its place.

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 annotations covering the destructive/mutating profile, the description needs only the core behavior plus the aspect-ratio rule, both of which are supplied. Remaining gaps, such as re-encode quality settings or confirmation of the default output location, are minor given the structured fields.

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 coverage is 100%, so every parameter already documents its meaning, including the aspect-ratio derivation behavior for width/height. The description largely restates that schema-level logic ('one side... or both') rather than adding new semantic detail, 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 and resource ('Resize a video... and re-encode') with the target dimensions made clear, so the operation is unambiguous. It does not name or distinguish itself from adjacent siblings like crop, reframe, or zoom, which is the only thing keeping it from a 5.

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?

The sentence 'Provide one side to keep the aspect ratio, or both to set an exact size' tells the agent how to use the width/height pair, which is useful implied usage. However, there is no guidance on when to choose scale versus siblings like crop, reframe, or export_preset, and no prerequisites or exclusions are stated.

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