Skip to main content
Glama

Valmera — agentic AI video editor

by io.valmera
OverviewDiscussionsAdmin

Set transitions

set_transitions
Idempotent

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Transitions at SCENE CHANGES — junctions where the footage actually changes shot, or where an insert (b-roll, title card, generated clip) splices in. All duration-preserving junction effects (footage never overlaps, timing never changes). IMPORTANT — after cut_silences a talking-head video has one junction per removed pause, and nearly all of them are JUMP CUTS inside one continuous shot: same framing, same subject, the speaker's head half a word further along. A jump cut works by being invisible. Putting a whip or a dip on each one fires a full-screen effect every couple of seconds through footage that never changed scene, and it reads as broken — a real user shipped 45 whips through one continuous shot and said so. scope defaults to 'scene' and handles this for you; the result tells you how many junctions it actually landed on and how many it skipped, so report THAT number, not the cut count. Pass scope='every_cut' whenever that stronger treatment serves the edit. Styles: 'dip_black' = quick dip through black (calm, universal); 'dip_white' = soft white fade-through; 'whip_left'/'whip_right' = fast directional slide with motion blur (energetic vlogs/reels); 'zoom_punch' = accelerating push through the cut (hype, sports); 'glitch' = RGB-split/noise burst (tech, gaming); 'flash' = additive white pop peaking ON the cut (beat-synced edits). duration_s 0.1-1.5 (default 0.3; keep whip/flash short, 0.15-0.4). 'none' removes them (hard cuts again). True crossfades (overlapping footage) are NOT supported — offer one of these instead and say so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNo'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.
styleYes
duration_sNo
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.
max_transitionsNoOptional 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.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only provide basic read-only, destructive, and idempotent hints. The description adds crucial behavioral context: the tool is project-scoped and returns the project identity and a count of landed vs. skipped junctions, explicitly telling agents to report that number. It also explains the risk of applying transitions to jump cuts and gives duration defaults (0.3) with specific guidance for whip/flash (0.15-0.4). This far exceeds the annotation coverage.

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?

The description is long but dense, front-loading the critical scope warning and returning-count instruction before enumerating styles. Every sentence adds information, though it could be tightened by moving some style details to the schema. The structure is logical: scoping, then styles, then duration, then exclusions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no output schema, the description covers everything an agent needs: project scoping, parameter semantics (styles, duration, scope), the returned information (landed/skipped counts), and a critical real-world pitfall (jump-cut over-application). It also addresses the unsupported case of true crossfades. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 67%, the description compensates fully: it explains every enum value for 'style' (dip_black, dip_white, whip_left/right, zoom_punch, glitch, flash, none) with visual/emotional intent, and provides the duration_s range (0.1-1.5, default 0.3) and specific guidance for whip/flash. It also clarifies the scope parameter's effect and the 'none' behavior. This goes well beyond the minimal enum listings in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sets transitions at scene changes, defines what counts as a scene change (shot changes or inserts), and distinguishes between 'scene' and 'every_cut' scopes. It lists all style options with visual meanings, making the purpose unmistakable and differentiating it from similar tools like set_fades.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is given for when to use scope='scene' versus 'every_cut', with a concrete warning about the over-application of effects on jump cuts from silence removal. It also instructs agents to report the landed/skipped junction count rather than the cut count, and notes that true crossfades are unsupported, directing users away from those requests.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Valmera — agentic AI video editor toolsInspect
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.

Resources