Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Add ui scene

add_ui_scene

Adds interface-based explainer scenes with timed layouts and identified objects that can morph across scenes. Metrics bind to supplied data or spoken values, and media slots reference real project recordings. Supports solid, dimmed or transparent backdrops.

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

Input Schema

NameRequiredDescriptionDefault
idNo
endNo
dataNoCSV text, rows or {name: number}
mediaNo
startNo
themeNo
accentNo
scenesYes[{at|word, layout, focus?, objects: [{id, kind, title|body|text|label|name|value|delta|state|from|bind|rows|rows_from|lines|aspect}]}]
backdropNo
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. Changed2 schema fields changed
    • addedInput schema / properties / data / type
      Added value: +[
+  "string",
+  "array",
+  "object",
+  "null"
+]
    • 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

B3.2/5.0
Behavior3/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive), so the description earns credit for added context: metrics bind to supplied data or spoken values, media slots must reference real project recordings, and backdrop can be solid/dimmed/transparent. It does not say whether repeated calls append or replace existing scenes, which matters 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.

Conciseness4/5

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

Three tight sentences, front-loaded with the core action and followed by behavioral constraints. No filler or restatement of the title, though the backdrop sentence is minor detail relative to the unexplained params.

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 complex tool with nested scene objects and no output schema, the description conveys the essential mental model: timed layouts, morphing objects, data-bound metrics, real media references. Gaps remain around how scenes append to a project and what start/end/theme/accent do, but the core behavior is conveyed.

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 only 30% across 10 parameters, so the baseline is lower, but the description does add meaning for three of them: data binding (data), media slots (media), and backdrop modes (backdrop). It says nothing about theme, accent, start/end, id, or project_id, leaving half the surface unexplained.

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 concrete verb and resource: 'Adds interface-based explainer scenes with timed layouts and identified objects that can morph across scenes.' This distinguishes it reasonably from the typography/text siblings, though it never names remove_ui_scene or set_typography_scene as the counterpart/alternative.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to siblings such as remove_ui_scene, set_typography_scene or add_device_stage. The agent must infer the use case from the purpose sentence alone.

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