Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Cut range

cut_range

Removes one source-time interval from the main video's current retained ranges and saves a new edit version. The remaining edit is preserved. Sound-safe boundary adjustments and optional word snapping are reported in the result.

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

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
snap_to_wordsNo

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. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation; the description adds real value on top by stating a new edit version is saved, that the remaining edit is preserved, and that sound-safe boundary adjustments plus optional word snapping are reported in the result. Since there is no output schema, disclosing that the result reports adjustments is genuinely useful. It does not say what happens to previously cut ranges or whether the caller must have an open project state.

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 short sentences, front-loaded with the action and outcome, with no filler. The only slight inefficiency is that the reporting sentence is compressed so far that it reads passively ("are reported in the result") without saying where or in what form.

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

Completeness3/5

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

For a four-parameter mutation with no output schema, the description covers outcome and side effects but leaves key gaps: units and timeline for start/end, whether the cut is clamped or rejected at boundaries, and how snap_to_words interacts with start/end. The explicit note about the project_id navigation pointer lives only in the schema, not the description.

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 only 25% (only project_id is documented), so the description must compensate. "Source-time interval" usefully implies start/end are measured on the source timeline rather than the edited timeline, which is meaningful added context, and "optional word snapping" names the role of snap_to_words. However, units (seconds?), inclusive/exclusive bounds, and out-of-range behavior are left unstated, so it does not fully cover the low schema coverage.

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?

"Removes one source-time interval from the main video's current retained ranges and saves a new edit version" gives a specific verb, target resource, and scope. It is clearly distinguishable in spirit from add_* siblings, though it never names its nearest relatives (cut_output_range, cut_silences, keep_segments, restore_range), so an agent must infer the boundary itself.

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?

The phrase "one source-time interval" and "main video" implies usage (single cut from the retained edit) but there is no explicit when-to-use/when-not guidance. Nothing tells the agent to prefer cut_silences, cut_output_range, or keep_segments instead in the situations where they overlap.

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