Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_status

Read-only

Retrieve the current status of an export job for a model using its model reference (owner/project/model, ul:// URI, or slug) and export ID.

Instructions

Get one export job's status for a model by owner/project/model, ul://owner/project/model, or slug with a project, plus the export id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesModel ref by owner/project/model, ul:// URI, or slug (requires project).
projectNoProject ref required when model is given by slug.
export_idYesExport job id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.12
    • changedInput schema / properties / export_id / description
      Previous value: -"24-character export job id."New value: +"Export job id."
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Model ref by owner/project/model, ul:// URI, or slug (requires project).",
+  "type": "string"
+}
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Project ref required when model is given by slug.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "export_id"
-]New value: +[
+  "model",
+  "export_id"
+]
  2. Changed1 schema field changedv0.1.6
    • addedInput schema / properties / export_id / description
      Added value: +"24-character export job id."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Get' is consistent with a safe read operation. The description adds no extra behavioral context such as polling semantics, response states, or authentication requirements, but the annotations cover the main safety profile.

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 a single sentence, front-loads the core action, and includes the essential addressing options without filler. Every phrase contributes to understanding what the tool does and how to invoke it.

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?

For a simple read-only status lookup, the description plus fully documented schema is largely sufficient to call the tool correctly. It does not explain the return format or what status values to expect, but the core invocation requirements are all covered.

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 description coverage is 100%, and the description largely restates what the schema already says about model refs and export_id. It adds no new meaning beyond the schema, so the baseline score applies.

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 ('Get'), a specific resource ('one export job's status'), and the supported model reference forms. It is clearly distinct from the sibling exports_list, though it does not explicitly name alternatives.

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?

It provides useful usage prerequisites: model can be given by owner/project/model, ul:// URI, or slug requiring a project, and export_id is needed. However, it does not say when to prefer this over exports_list, export_create, or export_cancel, so the selection context is only implied.

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