Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Open visual page

open_visual_page

Returns labeled pages from the main footage's persisted visual storyboard. With no explicit page selection, it returns pages not yet delivered in the current logical turn.

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

Input Schema

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

TDQS

B3.4/5.0
Behavior3/5

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

The phrase 'not yet delivered in the current logical turn' discloses a stateful, consuming behavior, which is meaningful next to the supplied annotations. However, the description never says pages get marked delivered after this call, what 'logical turn' scopes to, or whether repeated calls are safe. That leaves a non-idempotent, non-read-only tool under-disclosed.

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, front-loaded with the return value and followed by the default behavior. No filler. Slight density in 'persisted visual storyboard' but nothing that should be cut.

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?

There is no output schema, so the description carries the burden of explaining returns. It says 'labeled pages' but not what a page contains (label, image reference, timing, index), which is the key gap for an agent consuming the result. What it does say is accurate and consistent with annotations.

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 50%: project_id is documented in-schema while pages is not. The description adds the default-value behavior for omitted pages, which is real value. It says nothing about what the pages integers index into or how they map to labeled pages.

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?

States a specific verb and resource: returns labeled pages from the main footage's persisted visual storyboard. That is concrete and separable from pure-retrieval siblings like get_editorial_map or look_at. It stops short of defining what a 'page' actually is, so the resource remains partly jargon.

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 'no explicit page selection' clause implies the default usage path, which is genuinely useful. However, no alternative tool is named and there is no when-not guidance, e.g. how this differs from look_at, get_shots, or find_visual_moments for inspecting footage.

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