Skip to main content
Glama

export_project

Exports a timeline as a standalone editable Remotion project with source assets and an npm manifest, so you can customize and render it elsewhere.

Instructions

Export a standalone editable Remotion project with source assets and npm manifest.

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": "export_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 non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds real value by disclosing what the artifact contains (source assets, npm manifest), but says nothing about where files are written, whether outputDirectory is overwritten, or whether the operation is repeatable.

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 with no filler or redundancy. It is compact to the point of under-specification, but every word present earns its place.

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, but for a two-parameter export that writes files to disk the definition leaves too much open: no parameter meaning, no destination/overwrite semantics, and no routing versus export_video. The gap is significant relative to the tool's complexity.

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 the two required parameters, timeline and outputDirectory, so the schema gives bare names only. The description does not compensate at all — it never mentions the timeline input or clarifies whether outputDirectory must exist, is created, or is cleared.

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 resource: "Export a standalone editable Remotion project," and qualifies the output as containing source assets and an npm manifest. This distinguishes it reasonably from export_video (rendered output) without explicitly naming the sibling, so it lands just below the top of the scale.

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 statement of when to choose this over export_video or validate_export, and no prerequisites or exclusions. The agent must infer from the word "editable" that this is for handing off source rather than producing a finished file.

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