Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

export_file

Save Blender scenes or selected objects to 3D formats such as FBX, OBJ, GLTF, USD, STL, and more by setting a filepath and optional format or selection.

Instructions

Export scene or selected objects to a 3D file.

Supports FBX, OBJ, GLTF/GLB, USD, STL, PLY, Alembic (ABC), Collada (DAE), SVG, and X3D 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.

Returns: Dict with exported file path and format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
filepathYes
selected_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Changed1 schema field changedv1.2.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "export_fileDictOutput",
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the default for selected_only and the auto-detection behavior of type, which is genuinely useful, but it says nothing about overwriting an existing file, required permissions, or failure modes for an export that writes to disk.

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?

Front-loaded one-line purpose followed by formats, args, and return value, with zero filler. The Args/Returns scaffolding is standard but costs a few lines for only three parameters and could have been compressed.

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?

For a single-required-parameter export tool with a sibling import_file and an output schema, the description covers scope, formats, argument behavior, and return shape adequately. Only the file-overwrite and error-handling semantics are unaddressed, a minor gap given the tool's simplicity.

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

Parameters4/5

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

Schema description coverage is 0%, yet the description documents all three parameters meaningfully: filepath is an absolute path, type is an optional override auto-detected from extension, and selected_only defaults to False. The only slight redundancy is re-listing formats already present as the schema enum.

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?

States a specific verb+resource ('Export scene or selected objects to a 3D file') and enumerates the supported formats, so an agent immediately knows what the tool produces. It is cleanly distinguishable from siblings like import_file, save_file and render_image without opening 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 Guidelines3/5

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

Usage is implied by the scope clause ('scene or selected objects') rather than stated explicitly. There is no when-to-use/when-not guidance and no pointer to the natural alternatives (import_file, save_file), so the agent must infer the context.

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