Valmera — AI Video Editor

Set speed

set_speed

Idempotent

Changes playback speed over a main-video source-time interval, preserving audio pitch and re-anchoring program-time items. Overlapping speed spans are replaced and reported. Slow motion may duplicate frames when the source lacks sufficient frame rate.

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>",
      "factor": "<factor>",
      "project_id": "<project_id>"
    },
    "name": "set_speed"
  }
}

Input Schema

Name	Required	Description
`end`	Yes
`start`	Yes
`factor`	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'.

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

A3.7/5.0

Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety bar is partly met. The description still adds real behavioral context beyond that: audio pitch preservation, re-anchoring of program-time items, replacement and reporting of overlapping speed spans, and frame duplication during slow motion on low-frame-rate sources. That is substantive side-effect disclosure an agent could not derive from the annotations.

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?

Three tight sentences, front-loaded with the core action and followed by consequences and a caveat. Every clause carries information; no filler or restatement of the tool name.

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 mutating timeline tool with annotations covering safety and no output schema, the description covers the important behavioral edges: what gets overwritten (overlapping spans), what gets reported, and the pitch/frame-rate caveats. The remaining gaps are the undefined factor semantics and the absent comparison to set_speed_ramp, which keep it short of full completeness.

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 40%, with start, end, and factor undocumented in the schema. The description partially compensates by establishing that the interval is in source time rather than program time, and by implying via the slow-motion note that factor values below 1 are slow motion. It still gives no units, ranges, or constraints for factor, and does not define the relationship between start/end and the re-anchoring behavior.

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: changing playback speed over a main-video source-time interval, with the scope ('main-video') narrowing it meaningfully. It does not, however, distinguish itself from the sibling tools set_speed_ramp or remove_speed, so an agent must infer the boundary between a uniform speed change and a ramp.

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 by the scope phrase 'main-video source-time interval', which tells the agent this applies to the primary video track rather than overlays. There is no explicit when-to-use versus set_speed_ramp, no prerequisite statements, and no exclusions, so the agent gets context but no routing guidance.

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.