ServiceNow MCP Server

Overview Schema Source Related Servers Discussions Admin

List Ci

list_ci

Read-onlyIdempotent

List CMDB configuration items with optional class and query filters. Retrieve CIs by class name, encoded query, pagination, and selected fields.

Instructions

List CMDB configuration items with optional class and query filtering

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of CIs to return
`query`	No	Encoded query string (e.g., 'operational_status=1')
`fields`	No	Comma-separated list of fields to return
`offset`	No	Number of records to skip
`class_name`	No	CMDB class name (e.g., 'cmdb_ci', 'cmdb_ci_server', 'cmdb_ci_computer')	cmdb_ci
`display_value`	No	'false' (default) returns stored values; 'true' returns labels in place of sys_ids and choice values; 'all' returns {display_value, value} per field, which keeps the sys_id beside the name. query= still filters on stored values, not labels. With 'true' or 'all', dates come back in this identity's time zone and format	false
`response_format`	No	'detailed' (default) returns each reference field as {link, value}; 'concise' drops the link (an instance URL) and returns the sys_id alone	detailed

Output Schema

Name	Required	Description	Default
`note`	No
`class`	Yes
`count`	Yes
`records`	Yes
`warning`	No
`truncated`	No
`next_offset`	No
`display_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.9.2Oct 23, 2026

addedInput schema / properties / display_value

Added value: +{
+  "default": "false",
+  "description": "'false' (default) returns stored values; 'true' returns labels in place of sys_ids and choice values; 'all' returns {display_value, value} per field, which keeps the sys_id beside the name. query= still filters on stored values, not labels. With 'true' or 'all', dates come back in this identity's time zone and format",
+  "enum": [
+    "false",
+    "true",
+    "all"
+  ],
+  "type": "string"
+}

addedInput schema / properties / response_format

Added value: +{
+  "default": "detailed",
+  "description": "'detailed' (default) returns each reference field as {link, value}; 'concise' drops the link (an instance URL) and returns the sys_id alone",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "class": {
+      "type": "string"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "display_note": {
+      "type": "string"
+    },
+    "next_offset": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "records": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "class",
+    "records"
+  ],
+  "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.2/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds no behavioral context beyond the schema and annotations, such as pagination behavior or output shape, but it also does not contradict them.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity leaves out useful routing context rather than adding structure.

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?

The tool has seven optional parameters, rich schema descriptions, annotations, and an output schema. The description is minimally adequate because the structured fields carry most of the needed detail, but it does not help an agent decide when to use this list tool over sibling retrieval tools.

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 all seven parameters are already well documented in the input schema. The description only mentions class and query filtering, adding no syntax or meaning beyond what the schema provides, which matches the baseline of 3.

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 CMDB configuration items, with optional class and query filtering. It is clear what the tool does, but it does not distinguish itself from siblings like get_ci, list_records, or aggregate_records.

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 'optional class and query filtering' implies that filters can be used, but there is no explicit guidance on when to use this tool versus get_ci or list_records. No exclusions, prerequisites, or alternative routing are provided.

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