Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_status

Read-only

Retrieve one model export job's status by owner/project/model, ul:// URI, or slug with project, using the 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. Changed1 schema field changedv0.1.15
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+]
  3. Changed1 schema field changedv0.1.6
    • addedInput schema / properties / export_id / description
      Added value: +"24-character export job id."
  4. First observedv0.1.0

TDQS

A3.5/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, so the safe-read profile is covered by structured data. The description confirms it is a status lookup but adds nothing about polling cadence, status values, or terminal states. Adequate but thin given the lower bar set by annotations.

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?

A single front-loaded sentence with no filler; the object of the action precedes the identifier list. The phrasing is slightly dense ('plus the export id'), but nothing is wasted.

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 read-only lookup with full schema coverage and no output schema, the description covers what is needed to call it correctly. It could go further by naming the status values or terminal outcomes the job reports, but nothing essential to invocation is missing.

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%, so the three parameters and the three accepted model-ref forms are already documented in the schema. The description echoes those ref formats rather than adding syntax, constraints, or examples beyond them, so the baseline 3 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?

States a specific verb and resource: fetching the status of a single export job. The word 'one' sets it apart from exports_list, and the fetch semantics distinguish it from export_cancel. It stops short of explicitly naming those siblings, so a 4 rather than a 5.

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?

Usage is only implied: the agent can infer this is for polling a job after export_create and before/instead of export_cancel. There is no explicit when-to-use-versus-exports_list guidance and no stated conditions or exclusions.

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