AI3D Studio

List job download formats

list_job_files

Read-onlyIdempotent

List the files a finished job already has, one per format: the main result plus any alternate formats the model returned (for 3D models, for example glb with fbx or usdz), each with a public download URL. Pass format to find one format. This does not convert: if the format asked for is not there, available_formats says what is, and a model can be exported to other formats from the web app model viewer.

Input Schema

Name	Required	Description	Default
`format`	No	A file format to look for, e.g. 'glb' or 'stl'.
`job_id`	Yes	The job id returned by generate_3d or generate.

Output Schema

Name	Required	Description
`note`	Yes
`files`	Yes
`job_id`	Yes
`status`	Yes	pending and processing are running; success, partial, failed and canceled are final. 'partial' means some outputs finished and the rest were refunded.
`requested_format`	Yes
`available_formats`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 24, 2026
- removedOutput schema / properties / files / items / properties / content_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / files / items / properties / content_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / files / items / properties / format / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / files / items / properties / format / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / files / items / properties / size_bytes / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / files / items / properties / size_bytes / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / files / items / properties / source / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / files / items / properties / source / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / note / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / note / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / requested_format / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / requested_format / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 8, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds meaningful context beyond that by noting the job must be finished, that each format has a public download URL, and that the tool does not perform conversion. Those are behavioral constraints an agent needs before calling it.

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 front-loaded with the core purpose, then adds the format filter behavior and the non-conversion caveat. The sentences are dense but purposeful, with no filler.

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

Completeness5/5

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

Given the rich annotations, the output schema, and full input schema coverage, the description provides everything an agent needs: what the tool returns conceptually, how format is used, and where to go for conversion. No material gaps remain.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds operational meaning to format: it is a lookup filter rather than a conversion request, and if it is unavailable the response's available_formats field explains what exists. That goes beyond the schema's short format example.

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: it lists files a finished job already has, one per format, with public download URLs. It also distinguishes the tool from conversion by explicitly saying it does not convert, which separates it from convert_model.

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

Usage Guidelines5/5

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

It explains when to use the format parameter to target one format, what happens when the requested format is absent via available_formats, and redirects conversion/export needs to the web app model viewer. This gives clear usage boundaries and alternatives.

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

All AI3D Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?