Export Blender scenes or selected objects to glTF binary (GLB) format, with optional material inclusion for sharing or use in other applications.
Export to glTF binary (GLB) format.
Args: filepath: Output path. selected_only: Only export selected. export_materials: Include materials.
| Name | Required | Description | Default |
|---|---|---|---|
| filepath | Yes | ||
| selected_only | No | ||
| export_materials | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It confirms the export action and lists options, but does not mention side effects like file overwriting, the behavior when selected_only is false, or whether exported materials are embedded in the GLB. There is no contradiction with annotations, but the behavioral context is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, front-loaded with the purpose, and followed by a compact Args list with no filler. Every line contributes useful information, and the structure is easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple flat-parameter export tool, the description covers the essential inputs and format, but it omits return behavior, overwrite policy, and the exact meaning of the default selected_only=false. Since there are no annotations and no output schema, those gaps leave the description adequate but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% property description coverage, so the Args block is the primary source of parameter meaning. It explains all three parameters at a basic level: filepath is the output path, selected_only controls selection filtering, and export_materials includes materials. This successfully compensates for the otherwise undocumented schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the specific action and target format: 'Export to glTF binary (GLB) format.' This distinguishes it from format-specific siblings like export_fbx and export_obj, though it does not explicitly differentiate itself from the more general export_file tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus alternatives such as export_file, export_fbx, or export_obj. The intended use is only implied by the tool name and the format mentioned in the description, with no exclusions or conditional routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.