Skip to main content
Glama

Export long-form video

render_long

Export the project as a 16:9 1080p MP4 with the brand's end card, subtitles as SRT/VTT files and audio levelled to -14 LUFS. Costs 10 credits per started finished minute, charged when it completes; max_credits refuses a longer export. Returns render_id for get_render. It needs every graphic rendered: while any isn't, it starts their renders and returns status graphics_not_ready with their task ids instead. A still image waiting for its picture, or whose file is gone, is left out and listed as skipped_stills. Review the export two minutes at a time with review_render's from_seconds and to_seconds, or around_graphics to see each graphic and still.

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": {
      "project_id": "<project_id>"
    },
    "name": "render_long"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom create_project
max_creditsNoRefuse (start nothing) if the export's price in credits is above this: 10 per started finished minute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description carries substantial behavior the annotations cannot: a credit price of 10 per started finished minute charged only on completion, refusal semantics via max_credits, a hard precondition that every graphic be rendered, the graphics_not_ready status with task ids returned instead of a render, and skipped_stills for missing or pending stills. None of that contradicts readOnlyHint=false or destructiveHint=false. This is unusually rich disclosure for a non-idempotent mutation.

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?

The description is dense but front-loaded: output spec first, then cost, then return value, then preconditions, then review path. Most sentences earn their place. The cost-per-minute rule is stated twice (in prose and again in the schema), which is the main redundancy.

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 two-parameter export tool with no output schema, the description supplies everything an agent needs: the artifact produced, the return value (render_id) and its consumer (get_render), alternate status outcomes, and the review workflow. There is no meaningful gap left for an agent to guess at.

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 coverage is 100%, with both project_id and max_credits already documented in the schema including the same '10 per started finished minute' rule. The description adds no syntax or edge-case meaning beyond the schema, so it sits at the baseline.

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 opening sentence states a concrete verb and resource with full output specificity: 'Export the project as a 16:9 1080p MP4 with the brand's end card, subtitles as SRT/VTT files and audio levelled to -14 LUFS.' That is far beyond a restatement of the name. It does not, however, distinguish itself from the render_video, render_promo, or render_short_from_project siblings, so an agent still has to infer which renderer applies to long-form.

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?

It gives clear operational context: graphics must be rendered first, and review should go through review_render's from_seconds/to_seconds or around_graphics. Those are explicit routing instructions to named alternatives. What's missing is any statement of when NOT to use this tool, e.g. versus the other render_* siblings.

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