List model deployment records in your Ultralytics workspace to track and manage active and past deployments.
List model deployments in your Ultralytics workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No | Workspace owner; defaults to the account owner. |
Changes observed during successful MCP inspections.
v0.1.15Input schema / additionalPropertiesAdded value: +falsev0.1.12Does 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 clear. The description adds no behavioral context beyond what the annotations provide—no mention of pagination, filtering, or return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no wasted words. It is appropriately sized for a simple list tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation with one optional parameter and no output schema, the description is minimally adequate. However, it lacks context about when to choose this tool over siblings like deployment_get or models_list, leaving a gap in routing guidance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 the optional 'owner' parameter. The description does not mention this parameter or add any semantic detail beyond the schema; baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (List) and resource (model deployments) with scope (Ultralytics workspace). It clearly distinguishes from single-item tools like deployment_get, but does not differentiate itself from other list tools such as models_list or projects_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives (e.g., deployment_get for a single deployment) or when not to use it. Usage is only implied by the verb 'List'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.