Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Set insert window

set_insert_window
Idempotent

Changes an existing inserted clip's source offset, duration or playback rate in place. Rate-only changes preserve the selected source window while changing its program duration, with dependent timeline positions adjusted.

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": {
      "id": "<id>",
      "project_id": "<project_id>"
    },
    "name": "set_insert_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fitNo
cropNo
muteNo
rateNo
motionNo
rotationNo
duration_sNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
clip_start_sNo
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • addedInput schema / properties / motion
      Added value: +{
+  "enum": [
+    "none",
+    "zoom_in",
+    "zoom_out",
+    "pan_left",
+    "pan_right"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish non-destructive, idempotent, closed-world mutation, so the bar is lower; the description adds real value by disclosing a side effect beyond annotations – rate-only edits keep the source window while changing program duration and shift dependent timeline positions. It still doesn't say what happens to the other settings (fit, crop, mute, motion) when only some fields are supplied.

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 dense sentences with no filler, and the primary action is front-loaded before the ripple-behavior caveat. The wording is efficient, though "source offset" vs the schema's clip_start_s is slightly loose.

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 11-parameter mutation tool with no output schema and very thin schema descriptions, the description covers the headline behavior and timeline side effect but leaves seven parameters unexplained. An agent could call it with id/project_id but would have to guess at fit, crop, motion, or motion_motif semantics.

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 18% across 11 parameters, so the description must compensate and largely does not. It maps loosely to three fields (source offset ~ clip_start_s, duration ~ duration_s, rate ~ rate) but says nothing about fit, crop, mute, motion, rotation, or motion_motif.

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: "Changes an existing inserted clip's source offset, duration or playback rate in place". The phrase "existing inserted clip" and "in place" separates it from insertion/removal siblings, but no sibling (e.g. set_speed, move_insert) is named explicitly.

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 rather than stated: the tool operates on an already-inserted clip and is for offset/duration/rate edits. The note that rate-only changes preserve the source window hints at when this differs from a plain speed change, but there is no explicit when-to-use vs when-not or named alternative.

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