Skip to main content
Glama

Get render

get_render
Read-only

Status of a render_video or render_long job. With wait_seconds, waits until it finishes (up to 240s). Completed renders include download_url and checks: guardrails run on the finished file, such as the music cutting out. An error check means don't publish it. While a render_long export runs it also has parts (done, total, rendering, and retrying: any part being tried again, with its attempt and why the last one failed) and a one-line note saying the same.

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": {
      "render_id": "<render_id>"
    },
    "name": "get_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
render_idYes
wait_secondsNoMost agent clients stop waiting for a reply after about 60s

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that by describing the waiting behavior and its 240s ceiling, the fields returned on completion (download_url, checks), the meaning of an error check, and the parts/retrying structure for render_long. This is substantial behavioral disclosure that the annotations do not provide.

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 most important fact, that this is a status tool, comes first, followed by the wait behavior and then return contents. The final sentence about parts is dense and nests parentheses, but every sentence carries information an agent needs.

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

Completeness4/5

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

No output schema exists, so describing the return values (download_url, checks, parts, note) is exactly the right compensation, and the definition does it. It never enumerates the possible status values themselves (e.g., queued, rendering, failed), which is the one remaining gap for a status tool.

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 50%: wait_seconds already has a description, but the description reinforces its semantics ('waits until it finishes, up to 240s'). It also gives meaning to render_id implicitly by tying it to a render_video or render_long job, which compensates for the undocumented parameter.

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+resource ('Status of a render_video or render_long job') and explicitly names the two sibling tools whose jobs it reports on, so an agent can distinguish it from render_video/render_long and from review_render.

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 explains the wait_seconds behavior ('waits until it finishes, up to 240s') and adds a decision rule for error checks ('don't publish it'), which implies polling-then-publishing flow. However, there is no explicit guidance on when to use this versus check_jobs, review_render, or get_task, and no stated exclusions.

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