Valmera — AI Video Editor

Add zoom

add_zoom

Adds an eased camera move over a program-time interval with configurable framing, strength and motion style.

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": {
      "start": "<start>",
      "end": "<end>",
      "project_id": "<project_id>"
    },
    "name": "add_zoom"
  }
}

Input Schema

Name	Required	Description
`cx`	No
`cy`	No
`end`	Yes
`mode`	No
`rect`	No
`shake`	No
`start`	Yes
`ramp_s`	No
`rotate`	No
`purpose`	No	The nameable narrative or visible reason for this zoom.
`shake_hz`	No
`strength`	No
`overshoot`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`shake_decay`	No
`motion_motif`	No	Active Blueprint motion motif id this event executes; never 'hold'.
`target_evidence_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / project_id / description

Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."

Changed7 schema fields changedOct 9, 2026

changedInput schema / properties / mode / enum

Previous value: -[
-  "punch",
-  "ease",
-  "push_in",
-  "pull_out"
-]New value: +[
+  "punch",
+  "ease",
+  "push_in",
+  "pull_out",
+  "landing",
+  "pulse",
+  "shake"
+]

addedInput schema / properties / overshoot
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / ramp_s
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / rotate
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / shake
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / shake_decay
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / shake_hz
```
Added value: +{
+  "type": "number"
+}
```

First observedSep 9, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare it is a non-read-only, non-idempotent, non-destructive mutation, so the safety bar is partly covered. The description usefully discloses that the interval is in program time and that the move is eased, but says nothing about overlap/conflict behavior with existing zooms, how strength or shake interact, or what happens on repeated calls given idempotentHint=false.

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 front-loaded sentence with no filler or redundancy; every clause carries information. It is efficient, though its brevity is partly the cause of the coverage gaps rather than a virtue in itself for a 17-parameter tool.

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

Completeness2/5

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

With 17 parameters, no output schema, and low schema coverage, this complex timing/geometry tool needs much more explanation than one sentence. An agent would have to guess at time units, valid ranges, how cx/cy relate to rect, and what mode values like 'landing' or 'pulse' require.

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

Parameters2/5

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

Schema description coverage is only 18% across 17 parameters. The description names three conceptual knobs (framing, strength, motion style) which loosely map to rect/cx/cy, strength, and mode, but it leaves the units and semantics of start, end, ramp_s, overshoot, rotate, shake/shake_hz/shake_decay, and target_evidence_ids entirely undocumented in both schema and prose.

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 gives a specific verb and resource (adds an eased camera move) plus scope (over a program-time interval) and the tunable dimensions (framing, strength, motion style). It does not differentiate from close siblings such as add_zoom_path, remove_zoom, or punch_in_on_emphasis, so an agent cannot tell which zoom tool fits a given intent from this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. needing a project open, or an existing bound motion motif), and no routing to alternatives like add_zoom_path for path-driven moves. Usage is only inferable from the one-line purpose.

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

All Valmera — AI Video Editor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.