Valmera — AI Video Editor

Add strobe

add_strobe

Adds a frame-exact sequence of project images, source frames, program picture or colors over a fixed program window. Holding patterns and negation are configurable. Audio and program timing remain unchanged; high-frequency flashing requires the explicit flash-safety override.

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

Input Schema

Name	Required	Description
`end`	Yes
`fit`	No
`hold`	No
`start`	Yes
`frames`	No
`negate`	No
`pattern`	No
`as_insert`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`variant_set`	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."

AddedOct 15, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, non-idempotent operation. The description adds useful behavioral context beyond them: frame-exactness over a fixed window, unchanged audio/program timing, and the flash-safety override requirement for high-frequency flashing. It does not explain overwrite/undo behavior or failure/response details.

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?

The description is three sentences and front-loads the core add operation. The holding/negation sentence is somewhat under-specified, but no sentence is pure filler.

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?

For a 10-parameter mutation tool with a nested variant_set object and no output schema, the description is too thin. It omits most parameter semantics and any return/failure context, so it does not fill the low schema-coverage gap even though the annotations help with safety characteristics.

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 only 10%, with project_id the lone documented parameter, so the description needs to compensate and largely does not. It mentions holding patterns, negation, and a fixed program window only at a high level, leaving fit, as_insert, variant_set, frames item structure, start/end units, hold range, and enum meanings 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 operation: adding a frame-exact sequence of project images, source frames, program picture, or colors over a fixed program window. The frame-exact strobe window and configurable holding/negation distinguish it from generic add_* effects. It does not explicitly contrast with closely related siblings such as add_freeze_frame or add_color_screen.

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?

It provides a partial usage condition: high-frequency flashing requires the explicit flash-safety override, and audio/program timing remain unchanged. It does not say when to choose this tool over related add_* tools or when it should be avoided.

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.