Skip to main content
Glama

List Service Catalog Items

servicenow_list_catalog_items
Read-onlyIdempotent

Browse ServiceNow service catalog items with filters by category, name, or active status. Retrieve names, descriptions, categories, and prices with pagination.

Instructions

Browse available service catalog items.

Args:

  • query (string): Filter (e.g., 'nameLIKElaptop', 'category.titleLIKEhardware', 'active=true'). Default: all active items.

  • category (string): Filter by category title (partial match)

  • limit / offset: Pagination

  • response_format: Output format

Returns: Catalog items with name, description, category, and price

Examples:

  • Browse hardware items → category="Hardware"

  • Find software requests → query="nameLIKEsoftware"

  • List by category → category="Access & Permissions"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1–100, default 20)
queryNoEncoded query (default: active items)active=true
offsetNoNumber of results to skip for pagination (default 0)
categoryNoFilter by category title (partial match)
response_formatNoOutput format: 'markdown' (default) for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already mark readOnly/openWorld/idempotent, and the description adds default behavior ('all active items'), filter semantics (partial match), and return fields. No contradiction. It doesn't discuss pagination details or error cases, but with strong annotations this is acceptable.

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?

The description is compact and front-loaded with a one-sentence purpose, followed by short Args/Returns/Examples sections. No filler; every clause adds value, and examples are illustrative. Minor redundancy with schema defaults doesn't hurt.

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

Completeness5/5

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

For a list operation with no output schema, the description adequately explains what is returned (name, description, category, price) and how to constrain results. It covers query, category, pagination, and format. Missing edge cases are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description enriches parameters with concrete query syntax like 'nameLIKElaptop' and category partial-match behavior. It also clarifies response_format choices and pagination parameters. This goes beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The one-line description 'Browse available service catalog items' uses a clear verb and resource, and the title mirrors it. It differentiates from sibling tools like get_catalog_item (singular detail) and submit_catalog_request by scoping to browsing/listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides practical usage context: 'Browse hardware items → category="Hardware"' and query filter examples. It implies use for exploratory lookups of catalog items, though it doesn't explicitly mention alternatives/exclusions. It gives enough context to choose this tool over generic list or query tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kylburns89/servicenow-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server