Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_upload_video

Upload a local video as extracted frames to a dataset by slug, owner/slug, or URI. Reports the queued job ID and ingest status for follow-up.

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. Changed1 schema field changedv0.1.15
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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)."
  3. 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."
  4. Addedv0.1.6

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnly=false, idempotent=false, destructive=false). The description adds meaningful context beyond that: the signed-upload flow, that conflictPolicy silently defaults to skip, and that the operation is asynchronous (queued job id + current ingest status). This is good disclosure of a non-obvious default and return timing.

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?

Two dense, front-loaded sentences with no filler; the core action leads and the follow-up pointer trails. Slightly overloaded with parentheticals but each clause earns its place.

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?

There is no output schema, so the description correctly fills that gap by describing the return (queued job id and ingest status). Combined with the follow-up tool and the conflictPolicy default, it covers what an agent needs to invoke and then track the operation; minor gap on sibling differentiation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline. The description adds value by explaining the conflictPolicy default semantics ('defaults to skip; the platform default is undocumented'), which goes beyond the terse schema wording, and by restating accepted dataset ref formats.

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?

States a specific verb+resource ('Upload a local video as extracted frames') and clarifies the mechanism (signed-upload flow). It implicitly distinguishes itself from dataset_upload_file and dataset_upload_folder by scoping to video, but does not name those siblings to make the distinction explicit.

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?

Points to datasets_get for follow-up, which is useful context on sequencing. However, it gives no when-to-use-vs-alternative guidance (e.g. why choose this over dataset_upload_file or dataset_upload_folder for video content), leaving the choice to inference.

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