ServiceNow MCP Server

by jschuller

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List Update Sets

list_update_sets

Read-onlyIdempotent

Retrieve ServiceNow update sets with optional state and query filters to locate sets by status, name, or progress.

Instructions

List update sets with optional state and query filtering

Input Schema

Name	Required	Description
`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'

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`truncated`	No
`update_sets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.2Oct 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "update_sets": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "update_sets"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.7.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedv0.5.1Aug 1, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is fully covered; the description adds only the optional-filter behavior. It says nothing about default page size, maximum results, ordering of results, or whether filtering combinations are combined with AND.

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?

A single front-loaded sentence with no filler; every clause (list, state filter, query filter) maps to actual capability.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. What is missing for an agent to use it confidently is how this list relates to get_update_set and list_update_set_changes, and whether results are ordered or paginated beyond the limit cap.

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 already explains limit, query syntax examples, and state values. The description merely names two of the three parameters and adds no syntax or combination semantics beyond that baseline.

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?

The description states a specific verb and resource ('List update sets') plus the supported filters, so the core operation is unambiguous. It does not distinguish this tool from related siblings such as get_update_set (single fetch) or list_update_set_changes (child records), so an agent must infer the boundary.

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?

No explicit when-to-use guidance, no exclusions, and no pointer to alternatives like get_update_set for a single record. Usage is only implied by the word 'List' and the presence of filtering options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.