Skip to main content
Glama

auto_zooms

Adds automatic punch-in zooms to kept segments over a set length, alternating framing to make jump cuts feel intentional in the active edit.

Instructions

Automatic punch-ins for a cut edit: alternates framing between 100% and scale on each kept segment longer than every seconds, so jump cuts feel intentional. Adds them to the active editor.

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": {
      "planId": "<planId>"
    },
    "name": "auto_zooms"
  }
}

Input Schema

NameRequiredDescriptionDefault
everyNoOnly segments at least this long (s) get a framing change; default 4
scaleNoPunch-in percent, default 112
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the mutation target ('the active editor') and the alternating-framing rule, which is useful behavioral context. It does not say whether existing zooms are overwritten, what happens when no segment meets the threshold, or whether the operation is reversible.

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 sentences, front-loaded with the core behavior and followed by the side effect on the editor. No filler, and the threshold/scale logic is stated compactly.

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?

For a three-parameter tool with no output schema and no annotations, the description covers the mechanism and the mutation target adequately. The remaining gap is the return value and interaction with pre-existing zooms, which is minor given the tool's simplicity.

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 67%, with `every` and `scale` already documented in the schema. The description still adds real meaning by explaining how they interact: framing alternates between 100% and `scale` per segment exceeding `every` seconds. Only `planId` remains unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Automatic punch-ins for a cut edit') and describes the exact mechanism: alternating framing between 100% and `scale` on kept segments longer than `every` seconds. This is precise enough to distinguish it from a manual zoom-adding sibling without opening any schema.

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 description implies the context of use ('for a cut edit', 'so jump cuts feel intentional', 'adds them to the active editor'), which tells an agent this belongs after cuts are applied. However, it never states when not to use it, nor does it name or contrast with an alternative such as a manual zoom tool.

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