ServiceTitan MCP

crm_leads_list

Read-onlyIdempotent

Find CRM leads by ID, customer, status, prospect state, location, or created/modified date ranges. Get one paginated result set to identify leads needing follow-up.

Instructions

Search CRM leads by IDs, customer, status, prospect state, customer location, or created and modified ranges. Returns one page; use crm_leads_get for a known ID.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-delimited lead IDs
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`status`	No	Lead status
`pageSize`	No	Records per page (default 50)
`customerId`	No	Associated customer ID
`genPermUrl`	No	Generate permanent URL
`isProspect`	No	Filter by prospect state
`customerZip`	No	Filter by customer zip
`customerCity`	No	Filter by customer city
`includeTotal`	No	Include total count in response
`createdBefore`	No
`customerState`	No	Filter by customer state
`modifiedBefore`	No
`withoutCustomer`	No	Filter by missing customer/location
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`customerCreatedBefore`	No	Customer created before timestamp
`customerCreatedOnOrAfter`	No	Customer created on/after timestamp
`customerModifiedOnOrAfter`	No	Customer modified on/after timestamp

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.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description only needs to add extra behavioral context. It adds 'Returns one page', which tells the agent about pagination behavior beyond the schema, and the phrase 'created and modified ranges' clarifies date filtering semantics. No contradiction with annotations.

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?

Two sentences with no redundant words: the first states searchable dimensions, the second states pagination and the known-ID alternative. The most important usage information is front-loaded.

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 filtered read-only list endpoint, the description covers the main decision points: what it searches, that it returns one page, and when to switch to crm_leads_get. The output schema and rich parameter schema cover return and filter details, so no critical information is missing for an agent to invoke it.

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 80%, so the schema already documents most parameters. The description adds value by grouping filters semantically (customer location, prospect state, created/modified ranges), which helps an agent map intent to the less-documented date-time and location parameters. It does not delve into each parameter, but the schema covers the remaining details.

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 states a specific action ('Search CRM leads'), enumerates the key filter dimensions (IDs, customer, status, prospect state, location, date ranges), and notes it returns one page, which separates it from crm_leads_get. This clearly identifies the resource and operation without relying on the tool name alone.

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?

It explicitly gives an alternative for a known ID ('use crm_leads_get') and indicates the list is page-based, which implies pagination for large result sets. However, it does not mention when a bulk export sibling (e.g., export_leads) would be more appropriate, so the guidance is useful but not exhaustive.

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

Deploy Server