ServiceTitan MCP

crm_locations_list

Read-onlyIdempotent

Search service locations using filters like customer, name, address, coordinates, or date ranges to retrieve a paginated result list.

Instructions

Search service locations by IDs, customer, name, address, coordinates, external data, activity, or date ranges. Returns one page; use crm_locations_get for a known ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-delimited location IDs
`zip`	No	Filter by zip
`city`	No	Filter by city
`name`	No	Filter by location name
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`unit`	No	Filter by unit
`state`	No	Filter by state
`active`	No	Filter by active status	True
`street`	No	Filter by street
`country`	No	Filter by country
`latitude`	No	Filter by latitude
`pageSize`	No	Records per page (default 50)
`longitude`	No	Filter by longitude
`customerId`	No	Filter by customer ID
`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.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description only needs to add context beyond that. It adds useful operational detail by stating 'Returns one page', which tells the agent that results are paginated and that repeated calls may be needed for full result sets.

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 compact sentences that front-load the action and scope, then add the one-page behavior and the sibling alternative. Every sentence contributes useful information with no redundancy.

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 read-only search endpoint with well-described parameters and an output schema, the description covers the key behavioral points: it searches locations, returns one page, and routes known-ID lookups to crm_locations_get. The annotations handle safety semantics, so nothing critical is missing.

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 high, but the description meaningfully groups the 23 parameters into categories like address, coordinates, external data, and date ranges. It also covers the four date-time parameters that lack schema descriptions, helping the agent understand their intended use.

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 specifies a clear action ('Search service locations') and lists the filter dimensions, making the resource and operation unambiguous. It also distinguishes the tool from crm_locations_get by noting that the get variant is for a known ID.

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 identifies when to prefer crm_locations_get ('for a known ID') and frames this tool as a one-page search, which is the key decision an agent needs to choose between the closest alternatives. Other siblings are either unrelated or clearly export-focused.

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

Deploy Server