Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_upload_folder

Upload a local image folder as a zip to a dataset via the signed-upload flow. Optionally set target split or conflict policy, then get the queued job ID to track ingest status.

Instructions

Upload a local image folder as a zip 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.
folder_pathYesLocal path to image folder.
targetSplitNoTarget split for new images. Rejected if the folder itself has train/val/test subdirectories; use one or the other, not both.
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. Rejected if the folder itself has train/val/test subdirectories; use one or the other, not both."
  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. Addedv0.1.6

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false. The description adds meaningful behavior: the upload is asynchronous (queued job id), returns the dataset's current ingest status, and defaults conflictPolicy to skip. This goes beyond the structured annotations and helps the agent predict side effects.

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?

The description is two sentences, front-loaded with the core action and reference formats. It is mostly economical, though the parenthetical "(the platform default is undocumented)" adds some noise and slight confusion given the schema already documents the default.

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 4-parameter tool with full schema coverage and no output schema, the description covers the essential behavioral flow: upload, queued job id, ingest status, and follow-up via datasets_get. It does not explain authentication details or exactly how the zip is formed, but the signed-upload mention and follow-up guidance are sufficient for correct invocation.

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 dataset, folder_path, targetSplit, and conflictPolicy. The description mostly restates the dataset reference forms and conflictPolicy default that are already in the schema, adding little new parameter-level meaning.

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 first phrase names a specific action and resource: "Upload a local image folder as a zip through the signed-upload flow for a dataset." It also states the supported reference forms. It does not explicitly contrast with sibling tools like dataset_upload_file or dataset_upload_video, but the folder-vs-file/video distinction is strongly implied.

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 gives useful context such as folder uploads, the signed-upload flow, conflictPolicy defaulting to skip, and following up via datasets_get. However, it does not state when to prefer this tool over dataset_upload_file/dataset_upload_video or when not to use it, so usage guidance remains implicit rather than explicit.

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