Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_ingest

Start a remote dataset ingest job by providing a dataset reference and source archive URL. Configure conflict policy and target split, then retrieve the queued job ID for status follow-up.

Instructions

Start a remote URL ingest job 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.
sourceUrlYesRemote dataset archive or NDJSON URL.
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. Changed4 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 / sourceUrl / description
      Added value: +"Remote dataset archive or NDJSON URL."
    • 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. Changed1 schema field changedv0.1.6
    • addedInput schema / properties / dataset / description
      Added value: +"Dataset ref by id, slug, username/slug, or ul:// URI."
  4. Addedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavioral details beyond the annotations: this starts an asynchronous job, returns a queued job id plus current ingest status, and defaults conflictPolicy to skip. It also notes that the platform default is undocumented. This compensates well for the lack of an output schema while remaining consistent with the non-idempotent, non-read-only annotations.

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 two tight sentences with no filler. The action and accepted reference forms are front-loaded, followed by the default behavior and follow-up guidance. Every clause carries useful 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?

Given there is no output schema, the description adequately explains what the caller should expect: a queued job id plus current ingest status, and how to follow up. It covers the async nature and a key default. It could mention validation limitations or error behavior, but for a four-parameter ingest starter this is reasonably complete.

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 documents all four parameters. The description adds value for conflictPolicy by stating the default is skip and noting the platform default is undocumented, but it does not add meaning for dataset, sourceUrl, or targetSplit beyond what the schema provides. Baseline 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 opens with a specific verb and resource: 'Start a remote URL ingest job for a dataset,' then lists the accepted reference forms (slug, owner/slug, ul:// URI). This clearly distinguishes dataset_ingest from sibling upload and export tools.

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?

The description clearly frames the tool as the remote-URL ingest path, which differentiates it from local upload siblings like dataset_upload_file, dataset_upload_folder, and dataset_upload_video. It also gives an explicit follow-up instruction: 'use datasets_get to follow up.' It stops short of naming when-not-to-use alternatives, but the context is clear.

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