mcp-for-blender

Overview Schema Source Related Servers Discussions Admin

export_scene

Export Blender scenes, selected objects, or named objects to GLB or FBX files for use in game engines, viewers, or converters.

Instructions

Export the whole scene, the current selection, or named objects to a GLB or FBX file on disk,
so another application (a game engine, a viewer, a converter) can pick it up.

Parameters:
- filepath: Absolute path of the file to write (.glb or .fbx). Parent folders are created.
- format: "glb" (default; keeps PBR materials, emission, skins, shape keys, animation) or "fbx".
- object_names: Export only these objects (children included). Omit for selection_only or the whole scene.
- selection_only: Export what is currently selected in Blender (ignored when object_names is given).
- apply_modifiers: Bake modifiers on export. Use false for rigged / shape-key meshes.
- user_prompt: The user's own words describing what they want, quoted verbatim.

Returns JSON with path, bytes, selection_only and the exported object names.

Input Schema

TableJSON Schema

Name	Required	Default
`format`	No	glb
`filepath`	Yes
`user_prompt`	No
`object_names`	No
`selection_only`	No
`apply_modifiers`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 16, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses useful behaviors such as parent folder creation, selection_only precedence over object_names, and the effect of apply_modifiers. However, it does not state whether the operation modifies the Blender scene or overwrites existing files, leaving some behavioral gaps.

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?

The description is concise and well-structured: a single purpose sentence followed by a parameter list. All information is relevant and front-loaded, with no redundant phrasing.

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?

The description covers all parameters, mentions the return JSON fields, and gives practical usage tips. It is sufficient for an agent to call the tool correctly, though it omits edge-case behavior like file overwrites or error handling. Given the output schema exists, this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides detailed explanations for all six parameters beyond their schema titles, including defaults, precedence rules, and usage advice (e.g., 'false for rigged / shape-key meshes'), fully compensating for the 0% schema description coverage.

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?

The description clearly states the tool exports a scene, selection, or named objects to GLB or FBX files, specifying the exact resource and action. This distinguishes it from sibling tools like set_texture or get_viewport_screenshot, which have different purposes.

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?

The description provides parameter-level guidance (e.g., apply_modifiers for rigged meshes, selection_only precedence) but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied by the export purpose, but no explicit when/when-not guidance is given.

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