ServiceTitan MCP

inventory_warehouses_list

Read-onlyIdempotent

List warehouse definitions by page, filtering by IDs, active state, created or modified dates, and external data to resolve warehouse and inventory-location identifiers.

Instructions

List one requested page of warehouse definitions using IDs, active state, created or modified dates, and external-data mapping filters. Use this to resolve warehouse and inventory-location identifiers; use inventory transfers or purchase orders for stock movement and procurement.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated warehouse IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`externalDataKey`	No	External data key
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`externalDataValues`	No	External data values
`externalDataApplicationGuid`	No	External data application GUID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Sep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv2.5.1Apr 18, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description does not need to repeat safety traits. It adds the useful behavioral fact that the operation returns a single requested page of definitions rather than an unpaginated dump, but it does not go deeper into rate limits, expansion behavior, or open-world response characteristics. This is adequate but not especially rich.

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 two sentences with no filler. The first sentence front-loads the core operation and filter categories; the second sentence provides routing guidance to alternatives. Every clause earns its place.

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?

Given the annotations cover safety and the output schema covers return shape, the description sufficiently explains what the tool does, how it filters, and when it should be chosen over similar inventory tools. It is complete enough for an agent to select and invoke the tool correctly without further inference.

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?

The schema already documents 9 of 13 parameters with meaningful descriptions, and the parameter names are mostly self-explanatory. The description adds value by grouping the filters into categories ('IDs, active state, created or modified dates, and external-data mapping filters'), which helps an agent understand the intended filter families. However, it does not explain the less obvious parameters like includeTotal, createdBefore vs createdOnOrAfter, or pageSize defaults beyond what the schema provides.

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 description clearly identifies the tool as a read-only paginated list operation for warehouse definitions and enumerates the main filter dimensions (IDs, active state, dates, external-data mapping). It also differentiates the tool from related inventory operations by naming inventory transfers and purchase orders as the correct tools for stock movement and procurement, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

The description explicitly tells the agent when to use this tool ('resolve warehouse and inventory-location identifiers') and when to use alternatives instead ('use inventory transfers or purchase orders for stock movement and procurement'). This provides direct routing guidance and a clear exclusion condition.

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

Deploy Server