Maya MCP

Overview Schema Source Related Servers Discussions Admin

export_scene

Export a Maya scene or selected objects to ma, mb, fbx, obj, or abc files; set selected_only to limit output to the current selection.

Instructions

Export the scene or selection. export_type: ma, mb, fbx, obj, abc (Alembic). Set selected_only=true to export only selected 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": {
      "filepath": "<filepath>"
    },
    "name": "export_scene"
  }
}

Input Schema

Name	Required	Default
`filepath`	Yes
`export_type`	No	ma
`selected_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

A3.5/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. 'Export' implies writing a file, but the description does not disclose overwrite behavior, filepath requirements, directory creation, error behavior, or other side effects important for a write operation.

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 two short sentences and front-loads the core action. The format values and selected_only rule are compact and directly useful, with no wasted text.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for an export/write tool with no annotations and a required filepath parameter, the description omits key operational details such as overwrite behavior and filepath expectations.

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?

Schema description coverage is 0%, so the description must compensate. It documents export_type values and explains selected_only, but it leaves the required filepath parameter completely undocumented, including whether it must be absolute or what file extension is expected.

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 states a specific verb and resource: 'Export the scene or selection.' This clearly distinguishes it from siblings like import_file, render_scene, and get_scene_info. An agent can identify the operation 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?

It gives one useful usage rule: set selected_only=true to export only selected objects. However, it does not say when to use this tool versus alternatives such as render_scene or import_file, nor does it describe exclusions or prerequisites.

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