Skip to main content
Glama

export_asset

Exports selected or named Blender objects to a specified file path, with optional overwrite, enabling saving or sharing 3D assets.

Instructions

Export selected or named objects.

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": {
      "path": "<path>"
    },
    "name": "export_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
objectsNo
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/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 and largely fails to. It does not say where the export is written, what format is produced, whether an existing file is replaced, or what the return looks like — despite an 'overwrite' parameter that clearly implies a destructive file-writing side effect.

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?

A single short sentence, front-loaded with the action, with no filler. Its brevity is fine structurally; the problem is under-specification rather than wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter file-writing tool with no annotations and 0% schema coverage, the description is far too thin. An output schema exists so return values needn't be described, but destination path semantics, overwrite behavior, and selection-mode conditions are all absent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must supply parameter meaning. It only glosses the 'objects' parameter via 'selected or named'; the required 'path' (destination) and the 'overwrite' flag — the most safety-relevant parameter — are never explained in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Export selected or named objects" names a verb (export) and a resource (objects), and hints at the two selection modes via 'selected or named'. However, it does not distinguish this tool from close siblings like export_scene or export_selected_objects, so an agent cannot tell which export variant to pick from the description alone.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The phrase 'selected or named' weakly implies two invocation modes but never states the conditions that select them or how they relate to the sibling export tools.

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