Skip to main content
Glama

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.

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": {
      "job_id": "<job_id>"
    },
    "name": "list_job_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoA file format to look for, e.g. 'glb' or 'stl'.
job_idYesThe job id returned by generate_3d or generate.

Output Schema

NameRequiredDescriptionDefault
noteYes
filesYes
job_idYes
statusYespending and processing are running; success, partial, failed and canceled are final. 'partial' means some outputs finished and the rest were refunded.
requested_formatYes
available_formatsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed12 schema fields changed
    • 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"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: results are scoped to completed jobs, one entry per format, each carrying a public download URL. The non-conversion contract and the miss path (format absent -> consult available_formats) are the kind of failure-mode disclosure that saves a wasted round trip.

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 sentences, front-loaded with purpose before the usage and non-conversion notes; every clause carries information. The compressed phrasing around the format examples ('for 3D models, for example glb with fbx or usdz') reads slightly telegraphic but remains parseable.

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

Completeness4/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-shape explanation isn't required, and the definition covers the prerequisites, per-format granularity, and the miss case. For a two-parameter read tool this is close to fully specified; only the behavior for non-finished jobs is left implicit.

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 description coverage is 100%, so the baseline is 3; the description earns above that by explaining the semantics of format as a lookup filter rather than a request ('Pass format to find one format') and by describing what happens when it doesn't match. It still doesn't note the 16-char limit or case sensitivity, but the schema and description together are unambiguous.

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?

States a specific verb and resource ('List the files a finished job already has'), clarifies granularity ('one per format'), and adds the returned artifact ('public download URL'). The parenthetical glb/fbx/usdz example makes the format-per-file model concrete, and the explicit 'This does not convert' 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 Guidelines4/5

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

Gives a clear operating condition ('finished job'), tells the agent to pass format to narrow to one format, and explicitly excludes the conversion use case, redirecting to available_formats/web app instead. It doesn't say what to call instead when the job is still running (e.g. viewer_job_state), so the guidance stops just short of a full routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources