Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_upload_file

Upload a local dataset archive to Ultralytics Platform with optional target split and conflict policy, returning a job ID for follow-up.

Instructions

Upload a local dataset archive through the signed-upload flow for a dataset by slug, owner/slug, or a ul://owner/datasets/slug URI. Defaults conflictPolicy to skip (the platform default is undocumented). Reports the queued job id with the dataset's current ingest status; use datasets_get to follow up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetYesDataset ref by slug, owner/slug, or a ul://owner/datasets/slug URI.
file_pathYesLocal path to dataset archive file.
targetSplitNoTarget split for new images (overrides archive structure).
conflictPolicyNoConflict policy, e.g. "skip" (default), "keep_both", or "replace". Server-validated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.13
    • changedInput schema / properties / conflictPolicy / description
      Previous value: -"Conflict policy \"skip\" (default), \"keep_both\", or \"replace\"."New value: +"Conflict policy, e.g. \"skip\" (default), \"keep_both\", or \"replace\". Server-validated."
    • changedInput schema / properties / dataset / description
      Previous value: -"Dataset ref by slug, owner/slug, or ul:// URI."New value: +"Dataset ref by slug, owner/slug, or a ul://owner/datasets/slug URI."
    • addedInput schema / properties / targetSplit / description
      Added value: +"Target split for new images (overrides archive structure)."
  2. Changed2 schema fields changedv0.1.12
    • addedInput schema / properties / conflictPolicy
      Added value: +{
+  "description": "Conflict policy \"skip\" (default), \"keep_both\", or \"replace\".",
+  "type": "string"
+}
    • changedInput schema / properties / dataset / description
      Previous value: -"Dataset ref by id, slug, username/slug, or ul:// URI."New value: +"Dataset ref by slug, owner/slug, or ul:// URI."
  3. Changed2 schema fields changedv0.1.6
    • addedInput schema / properties / dataset / description
      Added value: +"Dataset ref by id, slug, username/slug, or ul:// URI."
    • addedInput schema / properties / file_path / description
      Added value: +"Local path to dataset archive file."
  4. Addedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

The description discloses meaningful behavior beyond the annotations: it uses the signed-upload flow, defaults conflictPolicy to skip, and reports a queued job id with ingest status rather than a synchronous completion. It also tells the agent how to follow up via datasets_get, which is valuable for an async upload operation.

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?

Two sentences carry the full functional description, default behavior, response expectation, and next step with no filler. The most important action and target are front-loaded, and every clause contributes information.

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 upload tool with no output schema, the description covers the essential operational details: what is uploaded, how the dataset is referenced, the conflict-policy default, what the response reports, and how to follow up. It does not explain the mechanics of the signed-upload flow, but that is likely a platform-level concern rather than a per-call requirement.

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 schema already explains each parameter. The description adds context about the default conflictPolicy and the upload flow, but these mostly echo or slightly extend what is already in the schema, so a baseline score of 3 is appropriate.

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 states a precise action and resource: uploading a local dataset archive through a signed-upload flow, with dataset addressing formats explicitly listed. This clearly separates it from sibling upload tools like dataset_upload_folder and dataset_upload_video, even without naming them.

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?

The description implies the intended use case by focusing on local dataset archives and the signed-upload flow, but it never explicitly states when to choose this tool over dataset_upload_folder, dataset_upload_video, or dataset_ingest. The follow-up instruction to use datasets_get is useful but is not an alternative-selection guideline.

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