Skip to main content
Glama
Sign In
agent-video-engine

agent-video-engine

by ferdy252
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

export_render

Render a final MP4 from a saved video project with captions, overlays, and mixed audio while preserving originals and preventing overwrites of newer edits.

Instructions

Render one final MP4 from the saved project, including captions, overlays and audio. Enabled automatic audio finishing levels main-track voice with saved adjustable controls, includes music/custom-layer audio in the master, and measures the encoded result. Always creates a new output and preserves originals and accepted exports.

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": {
      "projectDir": "<projectDir>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "export_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNo
presetNo
outputPathNo
projectDirYesAbsolute path of the local video project directory
concurrencyNo
expectedRevisionYesRevision returned by project_inspect. Prevents overwriting newer edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses real behavior: automatic audio finishing levels on the main track with saved adjustable controls, music/custom-layer audio included in the master, the encoded result being measured, and that it always creates a new output while preserving originals and accepted exports. That last point usefully clarifies the non-destructive footprint, though it does not cover cost/duration or whether the job is synchronous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in the first sentence, which is good. The second sentence is a dense, grammatically tangled run-on ("Enabled automatic audio finishing levels main-track voice with saved adjustable controls") that costs clarity without adding proportional value.

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 a six-parameter mutation tool with no output schema, the description covers the behavioral side reasonably (audio finishing, preservation of originals, measured result). It falls short on the option surface: preset, fit, outputPath, and concurrency are left entirely unexplained, so an agent must guess at export configuration.

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 only 33%, and the description adds nothing about the undocumented parameters. fit, preset, outputPath, and concurrency (with its 1-8 bounds) are never explained, so the agent gets no guidance on what these options change or what happens when they are omitted.

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 states a specific verb and artifact: "Render one final MP4 from the saved project, including captions, overlays and audio." That clearly separates it from preview-style siblings, though it never names preview_render or export_timeline as the non-final/partial alternatives, so the differentiation is implied rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: "final" and "from the saved project" suggest running this after editing is complete, and the schema note ties expectedRevision to project_inspect to avoid overwriting newer edits. There is no explicit when-not-to-use statement and no named alternative such as preview_render for checking output before a final export.

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

Deploy Server

Other Tools