Skip to main content
Glama

generate_remotion_project

Exports editable React/Remotion source code, validated timelines, and local assets from a given timeline and output directory, so you can build and render real Remotion video projects.

Instructions

Export actual editable React/Remotion source, validated timeline and local assets.

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>",
      "outputDirectory": "<outputDirectory>"
    },
    "name": "generate_remotion_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYes
outputDirectoryYes

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 this is a mutating, non-idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds that the timeline is validated and that local assets are emitted, which hints at failure modes and side effects on disk. It does not say what happens on an invalid timeline, whether existing output directories are overwritten, or that files are written to disk at all.

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 front-loaded sentence fragment with no filler, so nothing is wasted. It is arguably too spare given the tool's write behavior, but that gap is captured under completeness rather than conciseness.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a write tool with two required, entirely undocumented parameters and no statement of where files are written or what invalid input does, the definition leaves too much for the agent to guess.

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%, so the description carries the full burden, and it only gestures at 'timeline' and 'local assets'. It never clarifies whether timeline is a project ID, a file path, or serialized JSON, nor does it connect outputDirectory to where assets land. Two required parameters remain effectively undocumented.

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 verb 'Export' plus the concrete resource 'editable React/Remotion source, validated timeline and local assets' tells an agent exactly what artifact is produced, and the 'editable source' phrasing distinguishes it from the video/project export siblings by implication. It stops short of naming a sibling to route against, so it is clear but not fully differentiated.

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 guidance, no prerequisite (e.g. an existing analyzed timeline), and no mention of when export_video or export_project should be preferred instead. The agent must infer the call context entirely from the tool name and sibling list.

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