Valmera — AI Video Editor

Add region effect

add_region_effect

Applies a visual effect inside a defined region during a program-time window. Effects include color transformations, blur, pixelation and glass-like distortions; picture outside the region remains unchanged.

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

Input Schema

Name	Required	Description
`ev`	No
`id`	No
`end`	Yes
`scale`	No
`stage`	No
`start`	Yes
`colour`	No
`effect`	Yes
`region`	Yes	face\|card\|glyph:<motion id>\|rect:x0,y0,x1,y1\|ellipse:x0,y0,x1,y1, or FxRegion JSON (polygon points, keyframed keys)
`strength`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

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/5.0

Behavior3/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-idempotent, non-destructive, closed-world mutation. The description adds useful behavioral context by saying the effect is confined to a defined region and that picture outside the region remains unchanged. It does not explain compositing order, reversibility, whether effects replace or stack, or permission requirements, so it adds some value but leaves meaningful behavioral gaps.

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?

The description is two tightly written sentences with no wasted wording. The core action and timing are front-loaded, followed by a concise statement of supported effect categories and the region boundary behavior.

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?

This is a complex mutation tool with 11 parameters, only 18% schema description coverage, and no output schema. The description covers the central concept but omits important operational details such as parameter roles, effect ordering or stacking, interaction with existing region effects, and how removal works via remove_region_effect.

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 18% across 11 parameters, so the description needs to compensate but largely does not. It adds conceptual meaning for effect categories, region-scoped application, and the program-time window, but it does not explain ev, id, scale, stage, colour, strength, or the exact region syntax beyond what the schema already says.

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 uses a specific verb and resource: 'Applies a visual effect inside a defined region during a program-time window.' That clearly states what the tool does and distinguishes it from broad stylize or subject effects by emphasizing region containment. However, it does not explicitly name or differentiate from close siblings such as blur_region, add_subject_effect, or add_stylize.

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?

The description implies the tool is for region-scoped visual effects, but it gives no explicit when-to-use guidance, no when-not-to-use guidance, and no alternatives. An agent must infer whether to choose this over blur_region, add_stylize, add_subject_effect, or remove_region_effect.

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.