Maya MCP

Overview Schema Source Related Servers Discussions Admin

import_file

Import MA, MB, FBX, OBJ, or ABC files into a Maya scene; the file type is auto-detected from the extension when not specified.

Instructions

Import a file into Maya. import_type auto-detected from extension if not specified. Supported: ma, mb, fbx, obj, abc.

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": "import_file"
  }
}

Input Schema

Name	Required	Description	Default
`filepath`	Yes
`import_type`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

C2.9/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 burden. It discloses the useful auto-detection behavior and the allowed formats, but omits the critical mutation semantics for an import in Maya: whether the file is merged into the current scene or replaces it, and what happens on format mismatch. That omission is a significant gap for a scene-mutating tool.

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?

Two sentences, front-loaded with the action, with the format list tacked on efficiently. No filler, though the 'Supported: ...' fragment could be folded into a parameter note.

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, which the description correctly skips. But for a mutation tool with zero annotation coverage and a 0% documented schema, the definition is still thin — the scene-mutation behavior and filepath requirements are the missing pieces an agent needs before calling it.

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 coverage is 0%, so the description must compensate. It partially does for import_type (auto-detected from extension, valid values ma/mb/fbx/obj/abc), but filepath is completely undocumented beyond its name — no path format, absoluteness, or existence requirement. Partial compensation justifies a 3 rather than a 2.

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

Purpose4/5

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

States a specific verb and resource ('Import a file into Maya') plus the supported formats, which is enough to separate it from export_scene and create_object. It does not explicitly name the sibling it complements, but the import/export split is unambiguous.

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?

There is no statement of when to use this versus execute_maya_code or export_scene, no prerequisites (must the file exist on disk? absolute path?), and no exclusions. The only conditional guidance is about omitting import_type, which is parameter-level rather than tool-selection guidance.

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