Valmera — AI Video Editor

Set transitions

set_transitions

Idempotent

Sets duration-preserving effects at scene changes and inserted-media junctions. Footage does not overlap and the program's timing remains unchanged.

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": {
      "style": "<style>",
      "project_id": "<project_id>"
    },
    "name": "set_transitions"
  }
}

Input Schema

Name	Required	Description
`end`	No
`scope`	No	'scene' (default) = only where the footage changes shot or an insert splices in. 'every_cut' = every junction including silence-removal jump cuts; use it whenever that is the intended treatment.
`start`	No
`style`	Yes
`duration_s`	No
`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'.
`max_transitions`	No	Optional cap for a restrained treatment. The tool distributes the effect across at most this many eligible scene changes; use 2-4 when the user asks for subtle or not excessive transitions.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / end
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / start
```
Added value: +{
+  "type": "number"
+}
```

changedInput schema / properties / style / enum

Previous value: -[
-  "dip_black",
-  "dip_white",
-  "whip_left",
-  "whip_right",
-  "zoom_punch",
-  "glitch",
-  "flash",
-  "none"
-]New value: +[
+  "dip_black",
+  "dip_white",
+  "whip_left",
+  "whip_right",
+  "zoom_punch",
+  "glitch",
+  "flash",
+  "dissolve",
+  "slide_left",
+  "slide_right",
+  "none"
+]

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."

Changed1 schema field changedSep 18, 2026

addedInput schema / properties / max_transitions

Added value: +{
+  "description": "Optional cap for a restrained treatment. The tool distributes the effect across at most this many eligible scene changes; use 2-4 when the user asks for subtle or not excessive transitions.",
+  "minimum": 1,
+  "type": "integer"
+}

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 this non-destructive, idempotent, and mutating, so the baseline is covered. The description does add genuinely useful behaviour: the effect is duration-preserving, footage does not overlap, and program timing is unchanged. It still omits what happens to transitions already present, how many get placed by default, and whether the operation can be undone.

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 tight sentences with the constraint front-loaded and no filler. Slightly terse relative to an eight-parameter mutation tool, but nothing is wasted or padded.

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 an eight-parameter mutating tool with no output schema and half its parameters undocumented, the description is under-built. An agent cannot tell from it whether existing transitions are replaced, whether the call returns a list of affected cuts, or how style/scope/duration combine, so it would have to guess before invoking.

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?

With 8 parameters and only 50% schema description coverage, four parameters (style, start, end, duration_s) carry no explanation anywhere, and the description adds zero parameter meaning. It does not clarify what start/end bound, what units duration_s uses, or how style interacts with scope, so it fails to compensate for the coverage gap.

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 plus resource: it places duration-preserving effects at scene changes and inserted-media junctions. Clear enough to distinguish it from purely visual siblings like add_stylize, but it never differentiates itself from near-neighbours such as set_junction or set_fades, leaving ambiguity about which one handles a given cut treatment.

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?

The description gives no when-to-use guidance, no prerequisites, and no named alternatives. The only usage steering lives in the schema's 'scope' and 'max_transitions' descriptions, which the description neither references nor summarises.

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.