Skip to main content
Glama

video_transform_set

Correct squashed aspect ratios, rotate sideways videos, crop black bars with zoom/panscan, and deinterlace broadcast footage by setting video transform options.

Instructions

Fix a squashed aspect ratio, straighten a video recorded sideways, crop black bars, or deinterlace broadcast footage.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "video_transform_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYesaspect: "auto" | "16:9" | 1.78 · rotate: 0|90|180|270 · zoom: multiplier, 1 = fit · panscan: 0-1 · deinterlace: boolean

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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, and it does not disclose whether the change is immediate or requires re-render, whether it is reversible, what happens to unrelated transform settings, or what prerequisites (active video, codec support) exist. For a mutation tool with zero annotation coverage this is a substantial gap; the description functions only as an intent classifier, not a behavioral disclosure.

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?

A single compact fragment list with no filler, and the most common use case (aspect ratio) is front-loaded. It is slightly elliptical as a sentence and would read better with an explicit lead-in stating that exactly one name/value pair is applied per call.

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

Completeness3/5

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

For a small two-parameter setter whose schema already documents both parameters, the description covers the 'which transform for which problem' question adequately. It leaves the mutation semantics and the one-pair-per-call constraint unstated, and offers no hint about the companion get/reset tools that an agent would need to verify or undo a change.

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 50%, but the enum on 'name' and the inline per-key format notes on 'value' already document parameter shapes thoroughly. The description's real contribution is the problem-to-transform mapping (squashed ratio -> aspect, sideways -> rotate, black bars -> zoom/panscan, broadcast -> deinterlace), which adds genuine meaning for intent matching. It stops short of resolving ambiguity such as which of zoom vs panscan crops black bars.

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 conveys the resource and the effect concretely through four recognizable scenarios (aspect fix, sideways rotation, black-bar cropping, deinterlacing) that map cleanly onto the enum values aspect/rotate/zoom/panscan/deinterlace. It never states the operative verb ('set the named transform parameter to a value') and does not distinguish this setter from siblings like video_transform_get or video_transform_reset, so an agent must infer the write behavior.

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 scenarios imply when the tool is applicable, which is more than nothing, but they largely restate the enum members rather than describe decision conditions. There is no guidance on when not to use it, no mention of video_transform_reset for undoing a transform, and no prerequisite such as requiring a loaded video.

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