list_update_setsRetrieves ServiceNow update sets with optional filtering by state or custom query.
List update sets with optional state and query filtering
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of update sets to return | |
| query | No | Filter query (e.g., 'state=in progress', 'nameLIKErelease') | |
| state | No | Filter by state: 'in progress', 'complete', 'ignore', or 'default' |
Changes observed during successful MCP inspections.
v0.7.0Output schema / (root)Previous value: -{
- "additionalProperties": true,
- "type": "object"
-}New value: +nullv0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description is consistent with readOnlyHint and idempotentHint, but adds no extra behavioral context beyond 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single concise sentence, directly to the point.
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?
Clearly indicates the purpose and scope, though it does not describe the output format; acceptable for a list operation.
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 already covers parameter descriptions fully, so the tool description adds minimal extra meaning.
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?
Clearly states it lists update sets and mentions optional filtering, distinguishing it from related tools like list_update_set_changes and get_update_set.
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?
Provides basic context on filtering options but does not explicitly guide when to choose this over alternative listing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.