Valmera — AI Video Editor

Set frame

set_frame

Idempotent

Sets output aspect ratio and crop, padding or blurred-padding treatment. Crop focus uses source-frame fractions, with the top-left at zero. A centered focus is the default; output canvas dimensions do not imply additional detail in the source footage.

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": {
      "ratio": "<ratio>",
      "project_id": "<project_id>"
    },
    "name": "set_frame"
  }
}

Input Schema

Name	Required	Description
`mode`	No
`ratio`	Yes
`focus_x`	No
`focus_y`	No
`picture`	No
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.
`focus_track`	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."

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / picture

Added value: +{
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 4,
+  "minItems": 4,
+  "type": "array"
+}

First observedSep 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare it mutates but is idempotent and non-destructive, and the description remains consistent with that. Beyond the annotations it adds real behavioral context: focus coordinates are fractions of the source frame with top-left at zero, centering is the default, and enlarging the output canvas does not add source detail (an upscaling/quality caveat). It still says nothing about whether existing framing is replaced or how mode interacts with ratio.

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?

Three tight sentences with the core purpose front-loaded and the coordinate convention given immediately after. The final clause about canvas dimensions is a little oblique but earns its place as a quality caveat; no filler.

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 7-parameter mutation with no output schema and near-zero schema documentation, the description covers the ratio/crop intent and the coordinate system but omits the semantics of picture, focus_track, and the mode enum values. An agent could call it for a simple centered crop but would be guessing on animated focus tracks or picture rectangles.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (only project_id is documented), so the description must carry the load. It does explain focus_x/focus_y conventions (source-frame fractions, zero origin, centered default), which is genuinely useful, but leaves mode, ratio enum choices, the 4-element picture array, and the focus_track keyframe object entirely 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 first sentence names a specific verb and resource (sets output aspect ratio) and enumerates the treatment options (crop, padding, blurred padding), so an agent knows this configures framing. It does not distinguish itself from nearby siblings such as set_screen_frame, auto_reframe or deliver_aspects, which is the only thing keeping it from a 5.

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?

Usage is only implied: the mention of output aspect ratio and crop treatment suggests this is called when changing deliverable framing, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. auto_reframe for content-aware reframing, deliver_aspects for multi-aspect delivery). The agent must infer the ordering relative to render/export tools.

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.