Skip to main content
Glama

export_file

Exports Blender scenes or selected objects to 3D files (FBX, OBJ, GLTF/GLB, USD, STL, PLY, ABC), with format override and selected-only options.

Instructions

Export scene or selected objects to a 3D file.

Supports FBX, OBJ, GLTF/GLB, USD, STL, PLY, and Alembic (ABC) formats.

Args: filepath: Absolute path for the export file. type: Optional format override. Auto-detected from extension if empty. selected_only: If True, export only selected objects. Defaults to False. options: The exporter's own settings by name (true/false, numbers or choices; never text or paths). Common ones: glTF: export_draco_mesh_compression_enable, ..._level (0-10), export_image_format (AUTO, JPEG, WEBP, NONE), export_apply (apply modifiers), export_animations, export_yup. FBX: apply_unit_scale, global_scale, axis_forward, axis_up, use_mesh_modifiers, add_leaf_bones, bake_anim. OBJ: export_triangulated_mesh, apply_modifiers, export_materials, forward_axis, up_axis, global_scale. USD: export_materials, export_textures_mode, export_animation. STL: ascii_format, global_scale, apply_modifiers. An unknown name is refused with the exporter's full list.

Returns: Dict with exported file path and format.

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": {
      "filepath": "<filepath>"
    },
    "name": "export_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
optionsNo
filepathYes
selected_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / options
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Options"
      +}
  2. Changed1 schema field changedv3.0.0
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "ABC",
      -  "DAE",
      -  "FBX",
      -  "GLTF",
      -  "OBJ",
      -  "PLY",
      -  "STL",
      -  "SVG",
      -  "USD",
      -  "X3D"
      -]New value: +[
      +  "ABC",
      +  "FBX",
      +  "GLTF",
      +  "OBJ",
      +  "PLY",
      +  "STL",
      +  "USD"
      +]
  3. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "ABC",
      +  "DAE",
      +  "FBX",
      +  "GLTF",
      +  "OBJ",
      +  "PLY",
      +  "STL",
      +  "SVG",
      +  "USD",
      +  "X3D"
      +]
  4. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "export_fileDictOutput",
      +  "type": "object"
      +}
  5. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully explains option handling and that unknown option names are refused, but it does not disclose whether existing files are overwritten, whether parent directories are created, or other filesystem side effects.

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?

The description is front-loaded with the core action and formats, then organized into Args and Returns. The long options list is justified by the zero schema description coverage, though it makes the definition heavier than ideal.

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?

Given the complex exporter options and 0% schema coverage, the description is largely complete and includes return information despite an output schema existing. The main gap is lack of overwrite or filesystem side-effect disclosure.

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?

Schema description coverage is 0%, but the description compensates thoroughly: it explains filepath as an absolute path, type auto-detection, selected_only default, and options as exporter-specific settings with concrete examples and allowed value shapes. This is exactly the guidance the schema lacks.

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 gives a specific verb and resource: export scene or selected objects to a 3D file, and names supported formats. This clearly distinguishes it from import_file and save_file without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the tool exports either the scene or selected objects, explains format auto-detection, and documents default behavior for selected_only. It does not explicitly compare against siblings such as save_file or import_file, but the usage context is clear.

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

Deploy Server

Other Tools