Skip to main content
Glama

Render Job

render_job
Destructive

Polls an asynchronous render job to return its status and, when finished, the rendered image and metadata; pass discard=True after a terminal result to free resources.

Instructions

Poll an async render started by render_photoreal_submit.

Returns {job_id, status} where status is 'running', 'done', or 'failed'. When 'done', also returns {png_base64, png_path, renderer, view, material, width, height}; when 'failed', {error}. The result remains available for repeat polls.

Pass discard=True once you have a terminal result to free the job immediately (drops the cached image and closes its temp document); ignored while running. Jobs are also auto-evicted oldest-first once finished jobs exceed an internal cap.

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": {
      "job_id": "<job_id>"
    },
    "name": "render_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
discardNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark destructiveHint=true, and the description explains precisely why: discard=True drops the cached image and closes its temp document, is ignored while running, and jobs are auto-evicted oldest-first past an internal cap. It also discloses idempotent repeat-poll behavior and the exact return payloads per status, going well beyond the annotations.

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?

Front-loads the action and the originating tool, then layers return shape, then lifecycle/cleanup semantics. Every sentence carries operational information; nothing is restated from the schema or annotations.

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?

No output schema exists, yet the description enumerates the returned fields for running/done/failed states, so the agent knows exactly what to expect. Its remaining exposure (workspace scoping) is covered by the schema field description.

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 only 33% (just workspace), but the description compensates: it ties job_id to the submit tool and fully specifies discard semantics including the no-op case while running. The workspace parameter is left to the schema, which does describe it.

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?

Specific verb+resource ("poll an async render") plus the exact origin tool (render_photoreal_submit) that produces the job_id. An agent can tell immediately this is the polling counterpart to the submit tool, not a generic job tool.

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?

Says when to call it (after render_photoreal_submit), that repeat polls are valid, and when to pass discard=True (only after a terminal result). It does not address the generic job_status/job_result/job_list siblings, so the agent must infer which job API applies to renders.

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

Deploy Server

Other Tools