Valmera — AI Video Editor

Build podcast shorts from explicit story arcs

make_shorts

Creates locked child projects from explicit caller-authored source ranges and story context in a long recording. Over MCP, story arcs are supplied by the caller; the pipeline seeds those windows without selecting creative styling or rendering finished edits.

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": {
      "clips": "<clips>",
      "project_id": "<project_id>"
    },
    "name": "make_shorts"
  }
}

Input Schema

Name	Required	Description
`snap`	No
`clips`	Yes	Caller-authored story arcs. Required over MCP so the connected model chooses the shorts itself.
`count`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`style_note`	No	Optional audience or reference context to preserve for the eventual editor.

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

Changed5 schema fields changedOct 9, 2026
- addedInput schema / properties / clips / items / properties / end / minimum
```
Added value: +0
```
- addedInput schema / properties / clips / items / properties / start / minimum
```
Added value: +0
```
- addedInput schema / properties / clips / items / properties / title / minLength
```
Added value: +1
```
- addedInput schema / properties / count / minimum
```
Added value: +1
```
- addedInput schema / properties / snap
```
Added value: +{
+  "enum": [
+    "sentence",
+    "none"
+  ],
+  "type": "string"
+}
```
First observedSep 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive write, and the description adds real scope beyond them: it creates child projects, only seeds windows, and explicitly does not select styling or render. That is meaningful context about what the call does and does not cause. It omits whether repeated calls create duplicate child projects despite idempotentHint=false.

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 sentences, both front-loaded with the discriminating information (what is created, then what is deliberately not done). Slightly jargon-heavy ("seeds those windows") but no filler.

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 mutating tool with five parameters and no output schema, the description covers intent and boundaries but not results — an agent gets no hint about what is returned (child project ids? status?) or how to follow up with shorts_status or open_short after the call.

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 60%, so the schema already documents the most important fields (clips, start/end boundaries, project_id). The description reinforces that clips are caller-authored arcs the connected model must choose itself, which adds meaning. It says nothing about snap, count, or style_note.

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 opens with a specific verb+resource: "Creates locked child projects from explicit caller-authored source ranges and story context." That is far more informative than the title alone and separates it from siblings like suggest_story (creative selection) or shorts_status. It stops short of naming a sibling, so it lands at 4 rather than 5.

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?

"Over MCP, story arcs are supplied by the caller" implies the prerequisite condition — the caller must already have arcs — and "without selecting creative styling or rendering finished edits" implies what to do instead when you want creative selection. However, no alternative tool is named (suggest_story, open_short, apply_short_edit_batches), so routing is left to inference.

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.