Valmera — AI Video Editor

Keep segments

keep_segments

Replaces the retained source ranges in the given playback order and saves a new edit version. Repeated ranges repeat footage. Cut boundaries may be adjusted for word, sound and shot safety, with adjustments reported in the result; the word-snapping option controls additional alignment.

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": {
      "segments": "<segments>",
      "project_id": "<project_id>"
    },
    "name": "keep_segments"
  }
}

Input Schema

Name	Required	Description
`segments`	Yes
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`snap_to_words`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

First observedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations, the description adds important behavior: a new edit version is saved, repeated ranges repeat footage, cut boundaries may be automatically adjusted for word/sound/shot safety, and those adjustments are reported in the result. It does not cover permissions or edge cases, but with annotations already declaring mutation and non-idempotency, this is strong added context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three compact sentences and front-loads the core operation. Every sentence contributes useful information about mutation, repeated ranges, boundary adjustment, or snapping behavior.

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

Completeness4/5

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

For a mutating three-parameter edit tool with no output schema, the description covers the essential behavioral contract: it saves a new version, may adjust boundaries, reports adjustments, and explains repeated segments. Remaining gaps are exact segment format/time units and broader project-state prerequisites.

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

Parameters4/5

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

With only 33% schema description coverage, the description usefully explains non-obvious semantics for two parameters: segments define retained source ranges in playback order and repeated ranges repeat footage, while snap_to_words controls additional alignment. It still omits exact range formatting and time units, and project_id is left to 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 states a specific operation: replacing retained source ranges in playback order and saving a new edit version. It is clear what the tool does, but it does not explicitly distinguish itself from close siblings such as cut_range or restore_range.

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 and no named alternative for choosing keep_segments over cut_range, restore_range, or cut_output_range. The operation is inferable, but the agent receives no routing criteria.

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.