Blender Bridge

Export model for target editor

export_model

Export mesh models for web/Godot (GLB), Unity/Unreal (FBX), USD (USDZ), or 3D printing (STL in millimeters). Reports axes, units, file size and material warnings. GLB/FBX/STL respect scene unit scale; USD currently requires unit scale 1 and refuses other scales. Scene transforms stay unchanged; verify the file in the destination editor. Existing destinations are refused.

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>",
      "target": "<target>"
    },
    "name": "export_model"
  }
}

Input Schema

Name	Required	Description
`target`	Yes	Destination workflow: web/godot use GLB, unity/unreal use FBX, usd uses USDZ, print uses STL.
`filename`	No	Output filename for this result; choose a name appropriate to the requested format.
`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.
`selected_only`	No	Export selected mesh objects when true instead of the full supported mesh selection.
`operation_name`	Yes	Short, concrete history title in the user's language describing the requested operation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 / 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 / selected_only / description

Added value: +"Export selected mesh objects when true instead of the full supported mesh selection."

addedInput schema / properties / target / description

Added value: +"Destination workflow: web/godot use GLB, unity/unreal use FBX, usd uses USDZ, print uses STL."

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing refusal behavior for existing destinations, the USD unit-scale restriction, that scene transforms are left unchanged, what the report contains (axes, units, file size, material warnings), and a verify-in-destination-editor caveat. These are exactly the non-obvious side effects an agent needs before invoking an openWorld, non-idempotent export.

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?

Format mapping is front-loaded and nearly every sentence carries distinct information. Minor cost: the final fragment 'Existing destinations are refused' is clipped and ambiguous about what 'destination' means, and the blocking unit-scale caveat sits mid-paragraph rather than being surfaced first.

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?

With 6 params fully documented in schema, annotations covering safety, and no output schema, the description fills the important remaining gaps: format mapping, unit behavior, reported diagnostics, and refusal conditions. Only the overwrite/'existing destination' definition and file-location outcome are left slightly vague.

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 target, filename, project paths, selected_only and operation_name are already documented in structured form; baseline 3 applies. The description adds only marginal parameter meaning, notably 'STL in millimeters' and the USD unit-scale constraint tied to target.

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?

States a specific verb (export) plus the resource (mesh models) and enumerates the exact format per destination workflow (GLB/FBX/USDZ/STL), which is far more than a restatement of the title. It does not, however, distinguish itself from the sibling export_glb, leaving the agent to infer that this tool is the broader multi-format superset.

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?

Usage is implied through the target-to-format mapping and two hard preconditions ('USD currently requires unit scale 1 and refuses other scales', 'Existing destinations are refused'), which function as when-not rules. But no alternative tool is named (e.g. export_glb for the GLB-only case), so the agent must work out routing from sibling names alone.

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?