Skip to main content
Glama

Render a faceless video on a GPU

render_faceless_video

Render the final MP4 of a HyperFrames project made with the faceless-production or reel-studio workflow (get_workflow_instructions) on a GPU: about 1-3 minutes for a 60 s short, 3D included, instead of a CPU render in the workspace. Give projectDir (the folder with index.html, after cf-prep and hyperframes check pass); the MP4 lands at output (default renders/final.mp4 in projectDir) in the workspace. Each call waits up to 90 s and returns state running (with jobId and frame progress) or done; while running, call again with {jobId}. One render at a time per workspace. Billed as workspace time: 6 seconds of the monthly allowance per GPU second.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_faceless_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoWait on a render an earlier call started (fc-…)
outputNoWhere the MP4 goes, relative to projectDir or a workspace path (default renders/final.mp4)
projectDirNoThe HyperFrames project folder, e.g. ~/work/faceless/<slug>/edit or ~/work/shorts/<slug>/edit

Output Schema

NameRequiredDescriptionDefault
jobIdNo
stateNo
videoPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectDir / description
      Previous value: -"The HyperFrames project folder, e.g. ~/work/faceless/<slug>/edit"New value: +"The HyperFrames project folder, e.g. ~/work/faceless/<slug>/edit or ~/work/shorts/<slug>/edit"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly=false and destructive=false; the description contributes the operationally important facts an agent would otherwise have to discover: ~1-3 minutes for a 60 s short, a hard 90 s wait ceiling per call with running/done states, one render per workspace, and metered cost of 6 seconds of monthly allowance per GPU second. That is exactly the kind of behavior annotations cannot express.

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?

Nearly every clause carries load, and the key facts (what it makes, where, how long, how to poll, cost) are front-loaded. It is a single dense paragraph mixing prerequisites, async polling, concurrency, and billing, so a light bulleted separation would have improved scanability without adding words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a metered, asynchronous GPU render, the description covers prerequisites, return-state handling, concurrency limits, cost, and output destination, and an output schema exists so return value details need no duplication. Nothing an agent needs in order to call it and handle the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: projectDir must contain index.html and be past prep/check, and output defaults to renders/final.mp4 relative to projectDir or the workspace. It also frames jobId semantically as the resume handle for an in-flight render rather than just a string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and artifact ('Render the final MP4 of a HyperFrames project') plus the execution target (GPU) and the producing workflows (faceless-production / reel-studio). It explicitly contrasts with a CPU render in the workspace, so an agent can distinguish it from other video-generation siblings without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear precondition ('after cf-prep and hyperframes check pass') and points to get_workflow_instructions for the upstream workflow, plus the exact polling recipe (call again with {jobId} while running). It stops short of naming when NOT to use it, e.g. which sibling to pick for a CPU-only render or for other project types, and it doesn't reference save_faceless_video or the video_project_export family.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources