Valmera — AI Video Editor

Add overlay

add_overlay

Places an image or clip over the program picture during a program-time window. Supports picture-in-picture, logos, full-frame cover and picture-region fitting while retaining the underlying program audio and timing.

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": {
      "asset_key": "<asset_key>",
      "start": "<start>",
      "project_id": "<project_id>"
    },
    "name": "add_overlay"
  }
}

Input Schema

Name	Required	Description
`x`	No
`y`	No
`fit`	No
`exit`	No
`scale`	No
`start`	Yes
`opacity`	No
`z_index`	No
`entrance`	No
`asset_key`	Yes
`duration_s`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`source_crop`	No
`motion_motif`	No	Active Blueprint motion motif id this event executes; never 'hold'.
`source_start_s`	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."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / source_crop

Added value: +{
+  "items": {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  "maxItems": 4,
+  "minItems": 4,
+  "type": "array"
+}

addedInput schema / properties / z_index
```
Added value: +{
+  "type": "integer"
+}
```

Changed1 schema field changedOct 5, 2026
- changedInput schema / properties / fit / enum
```
Previous value: -[
-  "cover"
-]New value: +[
+  "cover",
+  "picture"
+]
```
First observedSep 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavior context by noting that underlying program audio and timing are retained, but it does not explain interaction with existing overlays, permissions, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, front-loaded with the core action and scope, with no filler. The supported overlay modes are listed compactly.

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?

A 15-parameter mutation tool with very low schema description coverage and no output schema needs more operational detail. The description establishes purpose but is insufficient to guide correct invocation of most parameters.

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?

With 15 parameters and only 13% schema description coverage, the description should compensate but does not. It conceptually maps to asset_key, start/duration, fit, and positioning, yet leaves x/y, scale, opacity, z_index, entrance/exit, source_crop, source_start_s, and motion_motif 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 specific verb and resource: "Places an image or clip over the program picture" during a program-time window, with supported overlay styles. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as add_element or add_text.

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?

Implies usage through the program-time window and supported scenarios (picture-in-picture, logos, full-frame cover, picture-region fitting). It gives no explicit when-not guidance or alternative-tool recommendations.

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.