Skip to main content
Glama

render_start

Start an MP4 render from a timeline: choose draft for a 540-wide preview or final for full quality, loudness-normalized output copied to the export folder.

Instructions

Render a timeline to MP4. quality 'draft' = fast 540-wide preview; 'final' = full quality, loudness-normalised, also copied to the export folder. Give timelineId (+version) or an inline timeline. Returns renderId + jobId.

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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
qualityNodraft
versionNo
timelineNo
timelineIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose a real side effect: 'final' is loudness-normalised and additionally copied to the export folder, so the agent knows an artifact lands outside the immediate result. It omits whether the call blocks, what the default 30s/max 45s wait window means, and whether renders are queued or rate-limited.

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

Conciseness5/5

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

Three compact sentences, front-loaded with the action, then the quality semantics, then the input options and return values. Every clause carries information and nothing is repeated from the schema.

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 five-parameter, async render tool with a nested object parameter and no output schema or annotations, the definition covers the quality tradeoff well but leaves the blocking behavior and the inline timeline structure unexplained. An agent could invoke it, but not confidently predict whether it must poll afterwards.

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

Parameters3/5

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

Schema description coverage is 0%, and the description compensates for only part of it: it explains both enum values of 'quality' and confirms the timelineId/version pairing. It says nothing about 'wait' (which plausibly controls blocking up to 45s) or the shape/contents of the nested inline 'timeline' object, so an agent must guess at two of five parameters.

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 ('Render a timeline to MP4') plus the return identifiers (renderId + jobId), so an agent knows exactly what action this initiates. No sibling tool overlaps with starting a render, so the action is unambiguous in context.

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?

It gives input-shape guidance ('Give timelineId (+version) or an inline timeline') and implicitly frames draft as the fast-preview choice, which helps an agent choose a quality. However, it never says when to prefer draft vs final, and despite returning a jobId it does not point the agent at job_status for polling, leaving the follow-up flow to inference.

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