Skip to main content
Glama

ai_modeling_export_batch

Exports owned 3D projects in one batch with individual receipts and a stable request_id, so repeated requests reuse the original job instead of duplicating work.

Instructions

export owned projects in one native batch, preserving individual receipts. 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_export_batch"
  }
}

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?

With readOnlyHint=false and openWorldHint=true already declaring a mutating, external-facing operation, the description still adds substantial context: request_id idempotency, that reuse returns the original job, that changed input conflicts, and that outcome_unknown must not be blindly retried. That is exactly the kind of retry-safety guidance annotations cannot express. It omits cost/billing behavior and what happens to already-exported projects in a partially failed batch.

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 short sentences, front-loaded with the verb and scope, and every clause carries information. A few phrases are telegraphic ('preserving individual receipts', 'changed input conflicts') and would benefit from one clarifying word each, but there is no filler.

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 batch mutation tool with a nested options object and no output schema, the description covers job/retry semantics well but leaves the credit cap and all export formatting options unexplained. An agent would have to read the raw schema to set max_estimated_credits or choose a format, which is the main completeness gap.

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% across three required parameters plus a nested 'parameters' object with seven documented-by-constraint-only fields (format, pack_uv, fbx_preset, texture_size, texture_packaging, export_orientation, export_vertex_colors). The description only explains request_id semantics well; max_estimated_credits — a required, safety-critical cap — is never explained, and none of the export options are mentioned.

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 names a specific verb and resource ('export owned projects') and adds scope ('in one native batch, preserving individual receipts'), which distinguishes it from a single-model export sibling. It stops short of naming which sibling to use for single or lite exports, so the differentiation is implied rather than explicit.

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?

'in one native batch' implies this is the multi-project option, and the idempotency notes tell the agent how to behave on retries. However, there is no explicit condition such as 'use this for 2-10 projects; use ai_modeling_model_export for one' and no prerequisites for the Studio account beyond the passing mention.

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