Valmera — AI Video Editor

Add time effect

add_time_effect

Adds picture-time effects such as reverse, echo, frame stepping, stutter, interpolation or remapping. Most modes preserve audio and program length; ramp mode changes picture and sound speed and re-anchors later material. Speech-sensitive modes require an explicit override over spoken words.

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": {
      "kind": "<kind>",
      "project_id": "<project_id>"
    },
    "name": "add_time_effect"
  }
}

Input Schema

Name	Required	Description
`id`	No
`end`	No	program s
`echo`	No	{count 2-8, spacing_f 1-6, decay 0.2-0.9}
`kind`	Yes
`word`	No
`curve`	No
`start`	No	program s
`factor`	No
`frames`	No
`repeats`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`allow_speech`	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."

AddedOct 16, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent, closed-world behavior. The description adds meaningful context beyond that: audio/program-length preservation by mode, ramp re-anchoring later material, and the allow_speech override requirement. It still omits removal/reversibility details and whether non-ramp modes insert or alter existing clips.

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?

Three tightly written sentences, front-loaded with purpose, then audio/program-length behavior, then the speech override. No filler; each sentence adds selection or behavioral context.

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?

For a 12-parameter mutation tool with nested echo, enums, low schema coverage, and no output schema, the description is too thin about parameter mapping and insertion/removal semantics. It covers mode-level behavior but not enough for reliable invocation without close schema inspection.

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 33% for 12 parameters, so the description must compensate. It clarifies ramp mode and the allow_speech override, but says nothing about factor, frames, repeats, word, curve, id, or how start/end delimit the effect; echo is described only in the schema.

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 uses a specific verb ('Adds') and resource ('picture-time effects') and enumerates example modes, so the agent knows this creates temporal effects rather than transitions or zoom. It does not explicitly contrast with close siblings such as set_speed_ramp or add_freeze_frame, so it is not 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?

It gives conditional behavior: most modes preserve audio and program length, ramp changes speed and re-anchors later material, and speech-sensitive modes need an explicit override. That helps mode selection, but it never states when to choose this tool over siblings like set_speed_ramp or add_freeze_frame, nor explicit when-not conditions.

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.