Valmera — AI Video Editor

Get editorial map

get_editorial_map

Read-only

Returns a compact source timeline joining sentences or shots with overlapping scene changes, energy, beats, vocal stress, pauses and measured visual-layout evidence. Supports indexed uploaded clips and focused views such as story, faces, interface regions or energy peaks.

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": "get_editorial_map"
  }
}

Input Schema

Name	Required	Description
`end`	No
`focus`	No
`limit`	No
`start`	No
`asset_key`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

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

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that output is a "compact" joined timeline and that it only works over indexed uploaded clips, which is useful behavioral context. It says nothing about how start/end/limit shape the result, truncation at limit=80, or whether the map is computed fresh versus cached (relevant given 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.

Conciseness3/5

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

Two sentences with no filler, but the first is a dense run-on list and phrases like "measured visual-layout evidence" are vague rather than informative. The capability that matters most – the focus selector – is buried in the trailing clause instead of being front-loaded.

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?

With six parameters, low schema coverage, no output schema and a non-idempotent read, the description should explain the time window, the limit cap and the clip scoping. It does not, so an agent cannot confidently construct a call beyond passing project_id and guessing at focus.

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 17% – only project_id is documented – so the description carries the burden for the other five parameters. It partially compensates for focus by naming story, faces, interface regions and energy peaks, but leaves 'all', 'quiet' and 'visual' unexplained. start, end, limit and asset_key get no mention at all, leaving the time-window and clip-scoping semantics undocumented in both places.

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 gives a specific verb+resource: it returns a compact source timeline joining sentences/shots with scene changes, energy, beats, vocal stress, pauses and layout evidence. That is a concrete data product, not a restatement of the name. It stops short of differentiating itself from siblings such as get_edl, get_shots or get_audio_analysis, which overlap heavily with this content.

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?

"Supports indexed uploaded clips and focused views such as story, faces, interface regions or energy peaks" describes capability, not when to reach for this tool. There is no statement of prerequisites (does it require indexing to be complete?), no exclusions, and no mention of which sibling to use instead for raw shots, transcript or audio analysis.

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.