Valmera — AI Video Editor

Add screen takeover

add_screen_takeover

Creates a continuous move into a screen visible in footage, with the supplied clip corner-pinned onto the screen and then handed off to full-frame playback. The effect combines the tracked screen plane, camera push and inserted clip.

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>",
      "at_output_s": "<at_output_s>",
      "project_id": "<project_id>"
    },
    "name": "add_screen_takeover"
  }
}

Input Schema

Name	Required	Description
`ease`	No
`push`	No
`hold_s`	No
`settle`	No
`corners`	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.
`at_output_s`	Yes
`clip_start_s`	No
`motion_motif`	No	Active Blueprint motion motif id this event executes; never 'hold'.

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

First observedSep 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds conceptual context about what the effect is composed of, but says nothing operationally useful: whether tracking must pre-exist, what failure looks like when no screen is detected, or why re-invocation is non-idempotent. No output schema exists to fill that gap.

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?

Two dense sentences, front-loaded with the verb and the visual outcome, with no filler. The second sentence is somewhat redundant with the first but does clarify the ingredient list.

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 an 11-parameter timeline mutation with no output schema and minimal annotation context, the definition is under-specified on prerequisites (tracked plane, project state), parameter meaning, and lifecycle (removal via remove_screen_takeover, interaction with set_screen_frame). It conveys the concept well but not enough to call it confidently.

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% (2 of 11 parameters), so the description bears the burden and only partially delivers. It implicitly maps 'supplied clip' to asset_key, 'corner-pinned' to corners, 'camera push' to push, and the full-frame handoff to duration/hold, but ease, settle, hold_s, clip_start_s, at_output_s, and motion_motif get no explanation beyond the schema's bare types.

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 names a specific verb and effect ('Creates a continuous move into a screen visible in footage') and explains the three-part composition: tracked screen plane, camera push, and inserted clip. An agent can picture the operation, though nothing distinguishes it from siblings like add_device_stage, set_screen_frame, or remove_screen_takeover.

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?

No when-to-use guidance, prerequisites, or alternatives are given. It never says that a screen must already be found/tracked (track_point, select_object, find_visual_moments) or when to prefer this over add_device_stage or set_screen_frame.

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.