Skip to main content
Glama

render_video

Render a bounded H.264 MP4 with Remotion while saving an editable project and progress log for review and reuse.

Instructions

Render a bounded real H.264 MP4 with Remotion and retain editable project and progress log.

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": {
      "timeline": "<timeline>",
      "output": "<output>"
    },
    "name": "render_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations already declare non-read-only, non-destructive, non-idempotent behavior. The description adds genuinely new context by disclosing that an editable project and a progress log are retained as side artifacts, and that the render is 'bounded'. It still does not explain what 'bounded' means (duration/resolution limits) or where artifacts land.

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?

One sentence, front-loaded with the action and artifact, with no filler. It is dense but every clause carries information, so only mild credit is lost for the unexplained 'bounded' qualifier.

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 mutation tool with two undocumented parameters and no usage routing, and an output schema exists so return values need not be described. Given the complexity of a video render, the definition should say more about input formats and render limits than it does.

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 0% for both required parameters, so the description must carry the meaning and it does not mention 'timeline' or 'output' at all. The parameter names are suggestive but there is no indication of format (timeline file vs inline JSON, output path vs URL), which is a real gap for a render tool.

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 ('Render') and a concrete artifact ('bounded real H.264 MP4 with Remotion'), plus the retained editable project and progress log. It does not differentiate itself from the close sibling export_video, which is the only clarity gap.

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 at all. With an export_video sibling in the catalog, an agent gets no signal about which of the two to pick or what prerequisites a render needs.

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