Valmera — AI Video Editor

Set typography scene

set_typography_scene

Idempotent

Creates or replaces a speech-cued mixed-font phrase as editable native text in one revision. Runs use absolute program-time cues and reserve their final positions; build and still modes control their appearance over the shared window.

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": {
      "id": "<id>",
      "start": "<start>",
      "end": "<end>",
      "lines": "<lines>",
      "project_id": "<project_id>"
    },
    "name": "set_typography_scene"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`box`	No
`end`	Yes
`fit`	No
`align`	No
`color`	No
`lines`	Yes
`start`	Yes
`motion`	No
`reveal`	No
`leading`	No
`font_size`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`mute_captions`	No

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

Changed17 schema fields changedOct 9, 2026
- addedInput schema / properties / box / items / maximum
```
Added value: +1
```
- addedInput schema / properties / box / items / minimum
```
Added value: +0
```
- addedInput schema / properties / fit
```
Added value: +{
+  "enum": [
+    "auto",
+    "strict"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / font_size / maximum
```
Added value: +0.2
```
- addedInput schema / properties / font_size / minimum
```
Added value: +0.03
```
- addedInput schema / properties / leading / maximum
```
Added value: +1.8
```
- addedInput schema / properties / leading / minimum
```
Added value: +1.05
```
- addedInput schema / properties / lines / items / properties / runs / items / properties / at / minimum
```
Added value: +0
```
- addedInput schema / properties / lines / items / properties / runs / items / properties / scale / maximum
```
Added value: +1.8
```
- addedInput schema / properties / lines / items / properties / runs / items / properties / scale / minimum
```
Added value: +0.6
```
- addedInput schema / properties / lines / items / properties / runs / items / properties / text / maxLength
```
Added value: +100
```
- addedInput schema / properties / lines / items / properties / runs / items / properties / text / minLength
```
Added value: +1
```
- addedInput schema / properties / lines / items / properties / runs / maxItems
```
Added value: +32
```
- addedInput schema / properties / lines / items / properties / runs / minItems
```
Added value: +1
```
- addedInput schema / properties / lines / items / properties / size / maximum
```
Added value: +1.8
```
- addedInput schema / properties / lines / items / properties / size / minimum
```
Added value: +0.6
```
- addedInput schema / properties / start / minimum
```
Added value: +0
```
AddedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Beyond the annotations the description adds real behavior: the operation replaces existing content, happens in one revision, advances on absolute program-time cues, holds reserved final positions, and has its appearance governed by build versus still mode. It does not say what happens to conflicting prior scenes or how the shared window interacts with captions, but the annotations already carry the safety profile (idempotent, non-destructive), so 3 is reasonable.

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?

It is only two sentences, leads with the core action, and has no filler; 'in one revision' is the right kind of compact behavioral detail. The jargon ('reserve their final positions', 'shared window') is dense enough that some clauses need a second read.

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 14-parameter mutation tool with nested line and run objects and no output schema, the description leaves key structure and timing semantics undocumented. It covers the conceptual model, cues, positioning, and reveal modes, but not the shape of what the agent must actually send.

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 coverage is 7% across 14 parameters, so the description has to carry nearly all of that load, and it does not. It implies what start and end mean as absolute program-time cues and suggests what reveal means, but box, fit, align, leading, font_size, motion, mute_captions, and especially the nested lines/runs structure with per-run at, font, scale, and color are left completely 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?

The description states a specific verb and resource: creates or replaces a speech-cued mixed-font phrase as editable native text, in one revision. This distinguishes it in kind from plain text tools, but it never names the closest siblings (set_typeset, add_typeset, add_kinetic_text, add_type_window), so an agent must infer the boundary itself.

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 and no alternatives are named. With a large family of overlapping text and typography tools, the agent gets nothing that tells it to prefer this tool over set_typeset or add_kinetic_text, or that this is the tool to use before remove_typography_scene.

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.