Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Add breakdown

add_breakdown

Adds a visual breakdown of the actual edit timeline with a live playhead, using the edit's real cut, graphics, camera, world and sound lanes.

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

Input Schema

NameRequiredDescriptionDefault
idNo
endNo
startNo
titleNo
followNo
positionNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

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

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context about what is actually created (real lanes, live playhead), but says nothing about whether it overwrites an existing breakdown, where it lands in the stack, or what a repeat call does 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?

A single front-loaded sentence with no filler, and the key noun phrase ("visual breakdown of the actual edit timeline") arrives immediately. It is efficient, though it spends its limited budget on descriptive color rather than the operational details an agent needs.

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?

This is a non-idempotent mutation tool with seven parameters and no output schema, yet the description omits where the breakdown is inserted, whether it is tied to a time range, and what happens on repeated calls. Given the very low schema coverage, the description leaves real gaps for correct invocation.

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 14% — just project_id is documented — so the description carries most of the burden and fails to explain any of the six undocumented parameters (id, start, end, title, follow, position). Terms like "live playhead" and "lanes" gesture at what the visual contains but give no guidance on how start/end or the top/bottom position enum change behavior.

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 uses a specific verb ("Adds") and a concrete resource ("a visual breakdown of the actual edit timeline with a live playhead"), and it names the data it draws from (cut, graphics, camera, world and sound lanes). It does not distinguish itself from any of the many sibling add_* tools, so an agent cannot tell from the text alone why it would pick this over add_overlay or add_hud.

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 statement of when to use this versus the ~140 siblings, no prerequisites, and no exclusions. The only usage signal is implicit in the word "adds", leaving the agent to infer that this is a post-edit visualization step.

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