Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_create

Create a model export job by specifying model and format. Confirm cost to queue the export; check export status for the final result.

Instructions

Create a model export job by owner/project/model, ul://owner/project/model, or slug with a project (state-changing, may cost credits). The format is validated immediately by the server; task and architecture compatibility is only known when the job runs, so a queued export can still fail. Use export_status and exports_list for the real outcome. Requires confirm_cost=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
halfNoLegacy FP16 export precision flag.
imgszNoImage size for export.
modelYesModel ref by owner/project/model, ul:// URI, or slug (requires project).
formatYesRequested export format (validated by the server).
dynamicNoDynamic input shapes.
projectNoProject ref required when model is given by slug.
gpu_typeNoGPU type required for TensorRT engine exports.
confirm_costNoMust be true to allow a credit-costing export job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.13
    • addedInput schema / properties / dynamic / description
      Added value: +"Dynamic input shapes."
    • addedInput schema / properties / half / description
      Added value: +"Legacy FP16 export precision flag."
    • addedInput schema / properties / imgsz / description
      Added value: +"Image size for export."
  2. Changed4 schema fields changedv0.1.12
    • changedInput schema / properties / format / description
      Previous value: -"Requested export format."New value: +"Requested export format (validated by the server)."
    • addedInput schema / properties / gpu_type / description
      Added value: +"GPU type required for TensorRT engine exports."
    • changedInput schema / properties / model / description
      Previous value: -"Model id, or slug when project is also provided."New value: +"Model ref by owner/project/model, ul:// URI, or slug (requires project)."
    • addedInput schema / properties / project / description
      Added value: +"Project ref required when model is given by slug."
  3. Changed3 schema fields changedv0.1.6
    • addedInput schema / properties / confirm_cost / description
      Added value: +"Must be true to allow a credit-costing export job."
    • addedInput schema / properties / format / description
      Added value: +"Requested export format."
    • addedInput schema / properties / model / description
      Added value: +"Model id, or slug when project is also provided."
  4. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the operation is state-changing and may cost credits, that format is validated immediately but compatibility is deferred until run time, and that a queued export can still fail. This gives the agent a realistic model of asynchronous behavior without contradiction.

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?

Three dense sentences front-load the core action and cost implications, then cover failure modes and follow-up tools. No filler or redundancy.

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 an async, state-changing operation with no output schema, the description covers cost, validation timing, deferred failures, and follow-up status checks. It does not mention the shape of the immediate response or how to obtain a job identifier, which is a minor gap given the tool's complexity.

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 baseline is 3. The description mostly restates schema content such as model ref formats, server-side format validation, and confirm_cost requirement, adding little new semantic value beyond what the schema already documents.

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 opens with a specific verb and resource: 'Create a model export job'. It clearly distinguishes this from the sibling tools export_status, exports_list, and export_cancel by framing it as the state-changing creation step, and it reinforces the distinction by pointing to status/list tools for the outcome.

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 explicitly tells the agent to use export_status and exports_list for the real outcome, which is direct guidance on how this tool fits versus alternatives. It also states the prerequisite confirm_cost=true, giving concrete when-to-use conditions.

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