Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dataset_images_list

Read-only

Retrieves images from an Ultralytics dataset by slug, owner/slug, or ul:// URI with filtering for splits, search, classes, labels, pagination, and image URLs.

Instructions

List images in a dataset by slug, owner/slug, or a ul://owner/datasets/slug URI with optional filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum images to return.
splitNoDataset split to filter by, for example train, val, or test.
offsetNoImages to skip.
searchNoImage name or metadata search.
datasetYesDataset ref by slug, owner/slug, or a ul://owner/datasets/slug URI.
classIdsNoClass IDs to filter by. An empty array is treated as no filter (all images match), not as a filter that excludes everything.
hasLabelNoFilter by annotation state.
includeImageUrlsNoInclude signed full-size image URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.15
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed8 schema fields changedv0.1.13
    • addedInput schema / properties / classIds / description
      Added value: +"Class IDs to filter by. An empty array is treated as no filter (all images match), not as a filter that excludes everything."
    • 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 / hasLabel / description
      Added value: +"Filter by annotation state."
    • addedInput schema / properties / includeImageUrls / description
      Added value: +"Include signed full-size image URLs."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum images to return."
    • addedInput schema / properties / offset / description
      Added value: +"Images to skip."
    • addedInput schema / properties / search / description
      Added value: +"Image name or metadata search."
    • addedInput schema / properties / split / description
      Added value: +"Dataset split to filter by, for example train, val, or test."
  3. Changed1 schema field changedv0.1.12
    • 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the accepted identifier forms, but this duplicates what the schema's dataset parameter already says. Pagination behavior (limit/offset) and return shape are undisclosed.

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?

A single front-loaded sentence with the action and resource leading. No waste, though its brevity comes partly from omitting genuinely useful detail rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter list tool with no output schema, the description covers the basics but adds nothing about pagination limits, how filters combine, or result ordering. Schema carries the parameter burden, but the description is thinner than the tool's complexity warrants.

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 fully documents all 8 parameters including the non-obvious empty-array semantics of classIds. The description's 'optional filtering' adds no syntax or meaning beyond the schema, so the baseline 3 applies.

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 (List) and resource (images in a dataset), and enumerates the accepted dataset reference forms (slug, owner/slug, ul:// URI). This is clear enough to distinguish from datasets_list or datasets_get, though it never names a sibling explicitly.

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?

The phrase 'with optional filtering' implies you can narrow results, but there is no when-to-use, when-not-to-use, or alternative routing guidance. The agent must infer the tool's place among 40+ siblings on its own.

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