Skip to main content
Glama

Render a promo's finals

render_promo

Renders the promo's final in the sizes you choose (9:16, 1:1, 4:5, 16:9) at 1080p, then checks each file. Each size is priced per scene (3 credits per started 2 s) plus 10 to put it together; the 9:16 draft is already its final, at no charge, if nothing changed since. Show the person each size's price (estimate_only) and let them choose. The balance must cover every size asked for, or nothing starts. It answers as soon as the renders start, with poll: call get_promo as it says until stage is done (about two minutes). review_render works on each final's render_id.

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": {
      "promo_id": "<promo_id>"
    },
    "name": "render_promo"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizesNoThe sizes to render (the promo's chosen sizes by default)
promo_idYesThe promo's id
wait_secondsNoHow long to wait for the finals (0 by default: it answers as soon as they start; the call never runs past about 45 s)
estimate_onlyNoGive each size's price and spend nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Goes well beyond the annotations by disclosing pricing (3 credits per started 2 s per scene plus 10 to assemble), all-or-nothing balance enforcement, and the free 9:16 draft when nothing changed. It also explains that the call returns as soon as renders start and that completion takes roughly two minutes via polling, which is exactly the behavioral context the readOnly/destructive hints cannot convey.

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?

Dense but front-loaded: purpose first, then pricing, then the polling follow-up. A few clauses are packed (pricing plus assembly fee plus draft waiver in two sentences) but every sentence carries operational information, with 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 paid, multi-size render with no output schema, the description supplies pricing, failure semantics (nothing starts unless balance covers all sizes), timing expectations, and the exact follow-up calls (get_promo, review_render). An agent can call this correctly and explain costs without further information.

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 baseline is 3; the description adds real meaning by framing estimate_only as the way to show prices and spend nothing, noting default sizes, and explaining why wait_seconds rarely matters (the call answers as soon as renders start). It does not restate the enum list in detail, but the schema already handles that.

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 the promo's final") plus the size options and post-render file checking, which clearly separates it from generic renderers like render_video or render_long and from preview/estimate siblings.

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

Usage Guidelines5/5

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

Gives an explicit workflow: call with estimate_only to show each size's price and let the person choose, then render, then poll get_promo until stage is done, then use review_render on each render_id. It also states the precondition that the balance must cover every size or nothing starts, so the agent knows when the call is viable.

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