Skip to main content
Glama

crop_zoom

Add a slow camera move to a finished clip by cropping and zooming in, out, left, right, up, down, or holding a still crop around a chosen focal point.

Instructions

A slow camera move on a finished clip. direction: in | out | left | right | up | down | none (a still crop). zoom 1.01-4. x, y (0-1) = the point to zoom on (0.5, 0.5 = the middle).

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": {
      "video": "<video>"
    },
    "name": "crop_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zoomNo
videoYes
directionNoin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this mutates state without being destructive. The description adds that the target must be a finished clip and that direction 'none' yields a still crop, but says nothing about whether a new file is produced, render time, or whether the source is overwritten.

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?

The core purpose is front-loaded in the first sentence and the remaining fragments are dense parameter notes with no filler. The telegraphic style is efficient but slightly clipped in places.

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 five-parameter mutation tool with no output schema, the definition covers parameter ranges well but leaves open what the call returns, whether the original clip is modified, and what prerequisites (existing rendered clip) apply. It is usable but not fully self-sufficient.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the load and mostly does: it enumerates the direction values, gives the valid zoom range (1.01–4), bounds x/y to 0–1, and explains that 0.5,0.5 is the centre with an anchor example. Only the 'video' parameter is left unaddressed, though its meaning is self-evident.

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 names the effect ('a slow camera move') and the target ('a finished clip'), which lets an agent tell this apart from clip-assembly or text/audio tools. It never names a sibling explicitly, but the verb-plus-resource statement is clear and specific.

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 phrase 'on a finished clip' implies this is a post-processing step applied after the clip exists, which is a genuine usage hint. There is no explicit when-to-use/when-not or mention of alternatives such as change_speed or fade, so guidance is only implied.

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