Blender Bridge

Render project image

render_project_image

Destructive

Render the receiving Blender scene to a PNG result at the requested project destination. Optional frame, width, height and samples control the render; operation_name is the user-facing history title. The call writes an output and explicit overwrite authorization is required to replace an existing destination. Long renders return a running request_id: poll get_blender_operation_status instead of repeating the render. Use take_screenshot for a quick viewport inspection without a final render, or get_project_file to retrieve an existing rendered result.

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": {
      "operation_name": "<operation_name>"
    },
    "name": "render_project_image"
  }
}

Input Schema

Name	Required	Description
`frame`	No	Scene frame to render.
`width`	No	Output image width in pixels.
`height`	No	Output image height in pixels.
`samples`	No	Requested render sample count.
`filename`	No	Output filename for this result; choose a name appropriate to the requested format.
`overwrite`	No	True only for a user-authorized replacement of an existing file.
`project_name`	No	Project name used to organize this output in the receiving Desktop workspace.
`project_path`	No	Absolute project folder only when the user explicitly supplied this external destination. Otherwise use Desktop’s configured workspace.
`operation_name`	Yes	Short, concrete history title in the user's language describing the requested operation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 23, 2026

addedInput schema / properties / filename / description

Added value: +"Output filename for this result; choose a name appropriate to the requested format."

addedInput schema / properties / frame / description
```
Added value: +"Scene frame to render."
```
addedInput schema / properties / height / description
```
Added value: +"Output image height in pixels."
```

addedInput schema / properties / operation_name / description

Added value: +"Short, concrete history title in the user's language describing the requested operation."

addedInput schema / properties / project_name / description

Added value: +"Project name used to organize this output in the receiving Desktop workspace."

addedInput schema / properties / samples / description
```
Added value: +"Requested render sample count."
```
addedInput schema / properties / width / description
```
Added value: +"Output image width in pixels."
```

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and non-idempotent, and the description supplies the operational context behind those flags: the call writes an output, replacing an existing destination requires explicit overwrite authorization, and long renders are async with a running request_id. That is meaningful disclosure beyond the annotation set.

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?

Four sentences, each carrying distinct information: what it does, how it mutates the destination, async polling behavior, and alternative tools. The core action and destination are front-loaded 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 9-parameter write tool with no output schema, the description covers the gaps that matter: side effects, overwrite authorization, async return behavior, and sibling routing. Nothing an agent needs in order to call this correctly is missing.

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 100%, so every parameter is already documented, including the overwrite authorization rule. The description mostly restates parameter roles (optional frame/width/height/samples, operation_name as history title) rather than adding syntax or constraints, which is the expected baseline-3 outcome when the schema does the heavy lifting.

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 the receiving Blender scene to a PNG at the requested project destination. It names the two nearest siblings (take_screenshot, get_project_file) and explains how this tool differs, so an agent can route without opening a schema.

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?

Explicitly says when to use the alternatives: take_screenshot for quick viewport inspection without a final render, get_project_file to retrieve an existing result. It also states the correct follow-up behavior for long renders (poll get_blender_operation_status instead of repeating the call).

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

All Blender Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?