Skip to main content
Glama
Mipiti MCP Server
by Mipiti

Get Export Status

get_export_status

Check whether an export job is still running or finished, and retrieve the completed file's download link, size, hash, and expiry details.

Instructions

The state of an export export_report started: running, or done and described. Read-only.

Done, it answers the file's filename, content_type, size, sha256, expires_at and download_url (a page of the web app where a signed-in person with access to the model downloads it; give the person that link), never the file itself. Running, status and poll_with. An export of another workspace, another person's, or one expired (an hour after it started) is not found.

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

Input Schema

NameRequiredDescriptionDefault
saveNoonce done, save the file in the exports folder, as ``export_report`` does. The locally run package only; the hosted server refuses it.
job_idYesthe export's ``job_id``.
server_versionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.108.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it declares read-only behavior, states that exports expire one hour after start, and explains that another workspace's, another person's, or an expired export is reported as not found. It also clarifies that ``download_url`` points to a web page requiring a signed-in user rather than the file itself.

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?

The text is front-loaded with the state summary, then the done-case fields, then the running-case fields, then failure conditions. The telegraphic phrasing ('Running, ``status`` and ``poll_with``') is compact but slightly terse, though no sentence is wasted.

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?

For a polling status tool, everything needed to call and interpret it is present: both states, the fields returned in each, expiry behavior, and not-found conditions. The return-value detail is arguably redundant with the output schema, but it adds useful semantics about the download link.

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 67%, and the description reinforces ``job_id`` as the export identifier and ``save`` as writing into the exports folder with the hosted server refusing it. However, ``server_version`` is undocumented in both the schema and the description, so the description only partly compensates for the coverage gap.

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 names a specific verb+resource (report the state of an export started by ``export_report``) and enumerates the two possible states, running or done. It is clearly distinguishable from the sibling ``export_report``, which starts the export rather than reporting on it.

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?

It establishes the workflow context: the export comes from ``export_report``, and while running the agent should use the returned ``poll_with`` value. It does not spell out explicit exclusions or timing guidance (e.g. how soon to poll), so it stops short of a full when/when-not treatment.

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