Skip to main content
Glama

Export Scene Asset

blender_export_asset

Export Blender 3D objects and scenes to multiple formats (FBX, OBJ, GLTF, STL, etc.) for sharing, backup, or use in other applications.

Instructions

Export Blender objects or entire scene to various 3D formats.

Comprehensive export tool with support for multiple formats and export options including materials and animations.

Args:

  • objects (optional): Object names to export (exports all if not specified)

  • format (enum): Export format (fbx, obj, gltf, glb, stl, ply, abc)

  • file_path (string): Export destination path (relative to project)

  • options (optional): Export options including modifiers, materials, and compression

Returns: Export confirmation with file size, format, and object count

Examples:

  • Export all: format="fbx", file_path="exports/scene.fbx"

  • Export specific: objects=["Cube", "Sphere"], format="obj", file_path="exports/selection.obj"

  • Optimized export: format="gltf", file_path="exports/optimized.glb", options={compression: 90}

Use when: Sharing assets, exporting for other applications, backup and version control Don't use when: Quick previews (use screenshot tools instead)

Performance: Varies by scene complexity and format, typically 5-30 seconds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectsNoObject names to export (exports all if not specified)
formatYesExport format
file_pathYesExport destination path
optionsNoExport options
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: performance characteristics ('typically 5-30 seconds'), confirmation of what gets returned ('Export confirmation with file size, format, and object count'), and practical use cases. While annotations cover basic hints (non-readOnly, non-destructive), the description provides operational insights that help the agent understand real-world behavior.

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 well-structured with clear sections (purpose, args, returns, examples, usage guidelines, performance). Every sentence adds value, with no redundant information. The front-loaded purpose statement immediately communicates the tool's function.

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?

Given the tool's complexity (4 parameters, nested objects, no output schema), the description provides comprehensive context: clear purpose, usage guidelines, parameter overview, return information, examples, and performance characteristics. It compensates well for the lack of output schema by describing what gets returned.

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?

With 100% schema description coverage, the baseline is 3. The description's 'Args' section mostly repeats schema information, though it adds minimal context about 'objects' exporting all if unspecified. It doesn't significantly enhance parameter understanding beyond what the schema already provides.

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 Blender objects or scenes to 3D formats, using specific verbs ('export') and resources ('Blender objects', 'entire scene', '3D formats'). It distinguishes from siblings like blender_get_screenshot (for previews) and blender_import_asset (for importing).

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?

The description explicitly provides 'Use when' scenarios (sharing assets, exporting for other applications, backup) and 'Don't use when' alternatives (quick previews, recommending screenshot tools instead). This gives clear guidance on when to choose this tool over other options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olbboy/claudekit-blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server