Skip to main content
Glama

render_motion

Renders motion-graphics templates to .mov video files with alpha and optionally inserts the result at a chosen timeline position.

Instructions

Render a motion-graphics template to a video file (.mov with alpha by default) and optionally place it on the timeline at placeAt (edited seconds).

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": {
      "template": "<template>"
    },
    "name": "render_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
trackNo
widthNo
heightNo
outputNoDefault ~/.openedit/renders/<template>-<time>.mov
paramsNo
placeAtNo
durationNo
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose the default output format (.mov with alpha), which is meaningful behavioral context. It says nothing about overwrite behavior, whether an existing file is replaced, render cost/duration, permissions, or how the optional timeline placement interacts with existing clips.

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?

A single well-structured sentence that front-loads the core action and appends the optional placement detail. Nothing is wasted, though the dense parentheticals could be split for easier scanning.

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 9-parameter tool with a nested free-form 'params' object, no annotations, and no output schema, the description is thin. An agent still cannot tell what fps/track/width/height default to, what 'params' accepts for the template, or whether the render overwrites prior output.

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 coverage is only 11% (just 'output'), so the description must compensate for eight undocumented parameters. It usefully clarifies that 'placeAt' is in edited seconds and that output is a .mov with alpha by default, but fps, track, width, height, params, duration, and template are never explained.

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 pairs a specific verb ('Render') with a specific resource ('a motion-graphics template') and names the output artifact (a .mov video file). The emphasis on 'template' implicitly separates it from sibling 'render' and 'render_caption_overlay', though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is referenced (e.g., plain 'render' or 'motion_templates'). The only usage hint is the optional 'place it on the timeline', which describes a mode of operation rather than criteria for selecting this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.