Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_upload_video

Upload a local video into a dataset by extracting frames, using dataset slug or URI, and returns a job ID for tracking.

Instructions

Upload a local video as extracted frames 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
fpsNoMaximum frame extraction rate in frames per second; may be reduced to keep the total within max_frames.
datasetYesDataset ref by slug, owner/slug, or a ul://owner/datasets/slug URI.
max_framesNoMaximum number of frames to extract.
video_pathYesLocal path to source video 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. Changed5 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 / fps / description
      Added value: +"Maximum frame extraction rate in frames per second; may be reduced to keep the total within max_frames."
    • addedInput schema / properties / max_frames / description
      Added value: +"Maximum number of frames to extract."
    • 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. Addedv0.1.6

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses meaningful behavior beyond the false annotation hints: it mentions the signed-upload flow, that the operation reports a queued job id, and that it returns the dataset's current ingest status. It also calls out that conflictPolicy defaults to skip even though the platform default is undocumented. These are useful behavioral details not present in the 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 three sentences with no filler: one for the core action, one for the conflictPolicy default, and one for the response shape and follow-up. It is front-loaded with the most important action and keeps each sentence focused.

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 upload tool with no output schema, the description covers the return shape ('queued job id with current ingest status') and points to datasets_get for follow-up. It is complete for core invocation, though it lacks authentication requirements and comparison guidance against sibling upload tools.

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 and the description need not compensate heavily. It does add one useful parameter-level detail: 'Defaults conflictPolicy to skip (the platform default is undocumented).' However, it does not enrich the semantics of fps, max_frames, targetSplit, dataset, or video_path beyond their schema descriptions.

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 specific verb and resource: 'Upload a local video as extracted frames through the signed-upload flow for a dataset.' It also specifies the accepted dataset reference formats and describes the video-to-frames nature, which distinguishes it from upload_file/upload_folder 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to choose this tool over siblings such as dataset_upload_file, dataset_upload_folder, or dataset_ingest. The only hint is post-usage: 'use datasets_get to follow up,' which is not an alternative-selection guideline. The intended use must be inferred from the action description.

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