Skip to main content
Glama

Render a launch film

render_launch_film
Destructive

Renders a film.json into film.mp4 beside it and writes film.timeline.json with each clip's start and length, so you can review a planned or changed launch film after rendering.

Instructions

Use it when the user wants a film.json rendered into film.mp4, after a plan or a change. Renders a film.json into film.mp4 next to it, with Chrome and ffmpeg on this machine, and writes film.timeline.json, each clip's start and length, which the result shows. It replaces the film.mp4 and film.timeline.json of an earlier render there and does not draw frames/ again. check_video makes a new sheet.png to look at. The film is 25 frames a second. Rendering a 30 second film takes one to three minutes. The launch-film playbook (makersmcp_playbook) has the whole job. (launch-film 0.3.1, on this machine.)

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": {
      "film": "<film>"
    },
    "name": "render_launch_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
filmYesThe film.json to render. film.mp4 and film.timeline.json go next to it.
jobsNoClips rendered at once (default 2). 1 suits a slow machine.
keepNoKeep the work files, each clip's MP4, in a launch-film-work- folder in the system's temp folder, outside the film's folder; the summary names it.
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / film / description
      Previous value: -"The film.json to render."New value: +"The film.json to render. film.mp4 and film.timeline.json go next to it."
    • changedInput schema / properties / jobs / description
      Previous value: -"Clips rendered at once (default 2)."New value: +"Clips rendered at once (default 2). 1 suits a slow machine."
    • changedInput schema / properties / keep / description
      Previous value: -"Keep the work files, each clip's MP4."New value: +"Keep the work files, each clip's MP4, in a launch-film-work- folder in the system's temp folder, outside the film's folder; the summary names it."
    • changedInput schema / properties / wait_seconds / description
      Previous value: -"How long to wait for the result before returning a job_id to wait on. 45 is safe for clients that stop a tool call after 60 seconds."New value: +"How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them."
    • addedOutput schema / properties / continued
      Added value: +{
      +  "description": "True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / docs
      Added value: +{
      +  "description": "The notes the text shows, and where each one is.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "description": "What to do next, as the Next line says.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "description": "When the download links stop working.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / files / items / properties / url
      Added value: +{
      +  "description": "Where to download the file, when the job ran on a server.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it overwrites the prior film.mp4 and film.timeline.json but leaves frames/ untouched, which directly explains the destructiveHint=true and non-idempotent profile. It also names the machine dependencies (Chrome, ffmpeg), the 25 fps output, the 1-3 minute runtime for a 30 second film, and the job_id continuation pattern. Missing only detail on failure modes or partial-render recovery.

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?

Front-loads the trigger and the effect, then layers in side effects, cost, and the playbook pointer in descending priority. Slightly dense in the middle sentence, but no filler.

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 mutating, minutes-long render with an output schema and rich annotations, the description covers trigger, outputs, overwrite scope, dependencies, duration, and the async wait path. An agent has everything needed to call it correctly and set expectations.

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 the schema already defines all four parameters; the description still adds value by explaining what film.timeline.json contains (each clip's start and length) and where the keep work files land relative to the film's folder. jobs and wait_seconds are not elaborated in prose, but the schema covers them adequately.

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?

States a specific verb and resource ("renders a film.json into film.mp4") plus the side artifact film.timeline.json, and explicitly contrasts it with the sibling check_video, which "makes a new sheet.png to look at." An agent can tell the two apart without opening either 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 trigger ("when the user wants a film.json rendered into film.mp4, after a plan or a change") and routes to the launch-film playbook for the full job. It lacks an explicit when-not statement, though the check_video contrast implicitly covers the nearest alternative.

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