Valmera — AI Video Editor

Add zoom path

add_zoom_path

Adds a continuous traveling camera move with at least two program-time keyframes. Each keyframe supplies a target rectangle or center and zoom strength, enabling holds and travel between subjects.

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": {
      "keyframes": "<keyframes>",
      "project_id": "<project_id>"
    },
    "name": "add_zoom_path"
  }
}

Input Schema

Name	Required	Description
`ease`	No
`purpose`	No
`keyframes`	Yes
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`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."

First observedSep 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the description is not carrying the safety burden alone. It adds real behavioral context — keyframes are program-time based, each carries a target rectangle/center plus zoom strength, and holds are supported — but says nothing about whether an existing zoom path is replaced or appended, or 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and constraint, and 'enabling holds and travel between subjects' earns its place by conveying the authoring intent. No filler or repetition of the title.

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 6-parameter mutation tool with no output schema and only 33% schema coverage, the description covers the key differentiator (keyframes) but leaves gaps on easing defaults, the role of target_evidence_ids, and the effect on any pre-existing zoom path. Adequate to attempt a call, not adequate 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 33%, so the description must compensate, and it partly does: the 'keyframes' array is an untyped object list in the schema, and the description explains that each entry supplies a target rectangle or center plus zoom strength. However, ease, purpose, and target_evidence_ids receive no explanation anywhere, leaving half the surface undocumented.

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?

States a specific verb and resource: 'Adds a continuous traveling camera move,' and pins the defining constraint of at least two program-time keyframes. It does not name the sibling it competes with (add_zoom, add_zoom_path's non-traveling counterpart), so an agent must infer the distinction from the keyframe requirement.

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?

Usage is implied rather than stated: the phrase 'traveling camera move' and 'holds and travel between subjects' hints at multi-subject sequences, while 'at least two keyframes' sets a minimum. There is no explicit when-to-use versus add_zoom, and no when-not guidance or prerequisites (e.g., project must be open).

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.