Skip to main content
Glama

ai_modeling_model_export

Export a Studio 3D model or animation to GLB, FBX, OBJ, STL, USDZ, or 3MF using your account, with a stable request_id to prevent duplicate export jobs.

Instructions

export a model or animation in a supported Studio format. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_model_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: idempotency keyed on request_id, the conflict-on-changed-input rule, and the outcome_unknown handling rule. It omits credit consumption (there is a max_estimated_credits field) and whether the job is asynchronous and how to poll it.

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?

Three compact sentences with the action front-loaded and the idempotency contract compressed into a single sentence. No wasted wording, though the third sentence packs three distinct rules together without separating them visually.

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?

For a complex export tool with a ~30-property nested schema, no output schema, and likely async job semantics, the description covers the idempotency contract but not the return shape, job polling, or credit cost. It is adequate to start a call but not to use the tool confidently end-to-end.

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?

Top-level schema description coverage is 0% for the three required parameters, and the description mentions none of them — not the format, the project scope, or the credit cap. The nested parameters object is large and dense, so the definition leaves the agent to infer which knobs matter and their interactions (e.g. fbx_preset vs format, texture_format vs format).

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?

The description states a specific verb and resource ('export a model or animation in a supported Studio format'), so the operation is unambiguous. It does not, however, differentiate itself from the many export siblings (ai_modeling_export_batch, ai_modeling_export_lite, ai_modeling_frontend_export), leaving the agent to guess which export path applies.

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?

There is real guidance about retry behavior (reuse returns the original job, changed input conflicts, outcome_unknown must not be blindly retried), which is valuable operating context. But there is no explicit when-to-use versus the sibling export tools, and no stated prerequisites beyond the passing mention of 'your Studio account'.

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