Skip to main content
Glama

add_zooms

Apply zoom or punch-in effects to main-camera clips over edited-timeline ranges to emphasize moments or conceal jump cuts.

Instructions

Add zoom/punch-in effects on the main camera over edited-timeline ranges (for emphasis or to hide jump cuts).

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": {
      "zooms": "<zooms>"
    },
    "name": "add_zooms"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomsYes

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?

No annotations are provided, so the description must carry the behavioral load; it does add meaningful context by naming the target ('main camera') and the coordinate space ('edited-timeline ranges'). However it is silent on whether existing zooms are replaced or appended when ranges overlap, whether a render is required afterward, and what the call returns.

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, front-loaded sentence with the action, target, and coordinate space stated before the optional rationale in parentheses. No filler whatsoever.

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 mutation tool with no annotations and no output schema, the description covers what and where but not the operational contract: overwrite-versus-additive behavior on overlapping ranges, ordering of multiple zooms, or whether rendering is needed to see the effect. Adequate to identify the tool, insufficient to predict its side effects.

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 reported at 0% and the top-level schema only defines the 'zooms' array, so the description has to compensate. It does clarify that the ranges are in edited-timeline time and implicitly that start/end form an interval, but it adds nothing about scale (percent punch-in) or ease (ramp seconds) that the nested properties describe.

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 states a concrete verb-plus-effect ('Add zoom/punch-in effects') and narrows the target to 'the main camera over edited-timeline ranges', so an agent knows exactly what is created and where it applies. It does not explicitly distinguish itself from the nearby auto_zooms sibling, which keeps it short of 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 parenthetical '(for emphasis or to hide jump cuts)' supplies the intent behind using this tool, which implies when it is appropriate. There is no explicit when-not guidance, no mention of the auto_zooms alternative, and no stated prerequisite such as having an edited timeline or clips already placed.

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