Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Set composite

set_composite
Idempotent

Updates how an existing motion graphic blends with the picture, including blend modes, footage-filled glyphs and ghost treatment for occluded text. Supplied settings merge with the existing composite.

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": {
      "motion_id": "<motion_id>",
      "project_id": "<project_id>"
    },
    "name": "set_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillNonext|previous|program[:s]|black|white|accent|#rrggbb|source:<s>|<asset key>[+loop], or FxSource JSON
blendNo
clearNo
fieldNo
ghostNoauto|off|{opacity,width_px,threshold}
stageNo
regionNoface|card|glyph:<motion id>|rect:x0,y0,x1,y1|ellipse:x0,y0,x1,y1, or FxRegion JSON (polygon points, keyframed keys)
opacityNo
fill_modeNo
motion_idYes
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Added

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, idempotent mutation, so the safety profile is covered. The description adds genuine value with 'Supplied settings merge with the existing composite,' which tells the agent that omitted fields are preserved rather than reset — a meaningful behavioral detail beyond idempotentHint. It says nothing about required permissions or whether 'clear' wipes the whole composite or a single field.

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 compact sentences, front-loaded with the mutation target and followed by the merge semantics. The mid-sentence list of features is informative rather than padding, though it reads as a partial parameter dump that stops short of the full set.

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 mutation with no output schema and low schema description coverage, the description is adequate but thin. It establishes merge semantics and the broad purpose, but leaves the interaction between clear/field and the other settings, and the meaning of region/stage, unexplained for an agent to guess at.

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 coverage is only 36% across 11 parameters, so the description should carry more weight than it does. It does add meaning to three of them — 'footage-filled glyphs' explains fill, 'blend modes' explains blend, and 'ghost treatment for occluded text' explains ghost — but clear, field, stage, region, opacity, and fill_mode are left to their terse schema entries or bare names.

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 target (updates an existing motion graphic's compositing/blending) and enumerates the aspects covered: blend modes, footage-filled glyphs, and ghost treatment. That distinguishes it from sibling add_motion_graphic, but it never draws the boundary against the adjacent set_motion_graphic or set_text_motion tools.

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 phrase 'an existing motion graphic' implies a prerequisite (the graphic must already exist, and motion_id must reference it), but there is no explicit when-to-use guidance, no exclusions, and no routing to set_motion_graphic for non-composite changes. The agent must infer the boundary from tool names alone.

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

Resources