Valmera — AI Video Editor

Set junction

set_junction

Idempotent

Sets or removes a duration-preserving cut device at specified program junctions. Each cut has one device, replacing the previous selection; sound and program timing remain 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_junction"
  }
}

Input Schema

Name	Required	Description
`at`	No
`end`	No
`cuts`	No
`only`	No
`count`	No
`start`	No
`style`	Yes
`colour`	No
`origin`	No
`duration`	No
`direction`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026
- removedInput schema / properties / end / minimum
```
Removed value: -0
```
- addedInput schema / properties / only
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / start / minimum
```
Removed value: -0
```

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / end

Added value: +{
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / start

Added value: +{
+  "minimum": 0,
+  "type": "number"
+}

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 15, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds real value by disclosing that each cut holds exactly one device, that a new selection replaces the previous one, and that sound and program timing are preserved. It still omits prerequisites, valid device styles, and how removal is expressed, which matters for a 12-parameter mutation.

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 compact sentences, front-loaded with the action and the invariant. No filler, though 'cut device' and 'program junctions' could have been grounded with a single clarifying clause rather than left as jargon.

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 8% schema coverage and no output schema, the description is far too thin. It never explains the required style or project_id semantics, what values are legal, how 'removes' is requested, or what happens when the junction already has a device, leaving the agent to guess at invocation.

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 description coverage is only 8% across 12 parameters, so the description must carry the burden, and it largely does not: at, cuts, only, start, end, count, origin, duration, direction, and colour are never explained. The only meaningful hints are that junctions are 'specified' (pointing at at/cuts) and that timing is preserved (constraining duration/start/end). It adds marginal, not sufficient, meaning beyond 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 gives a specific verb pair ('sets or removes') and a specific resource ('duration-preserving cut device at specified program junctions'), so the agent knows this is a junction-level device mutation, not a text/transition/effect tool. It stops short of differentiating itself from adjacent siblings such as set_transitions, add_device_stage, or set_insert_window, and 'cut device' is unexplained domain jargon.

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 explicit when-to-use guidance, no when-not conditions, and no named alternative among the many sibling tools. The agent must infer from the word 'junction' that this applies only at program junctions, and the phrase 'sets or removes' leaves the selection criteria for removal entirely unstated.

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.