ServiceTitan MCP

crm_contacts_list

Read-onlyIdempotent

Search CRM contacts by name, title, reference ID, archive status, or date ranges. Retrieve paginated results to find specific contacts.

Instructions

Search CRM contacts by name, title, reference ID, archive status, or date ranges. Returns one page; use crm_contacts_get for a known UUID.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Filter by contact name
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`title`	No	Filter by contact title
`pageSize`	No	Records per page (default 50)
`isArchived`	No	Filter by archive status
`referenceId`	No	Filter by external reference ID
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No

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.0

Behavior3/5

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

Annotations already cover read-only, non-destructive, idempotent, and open-world behavior, lowering the burden on the description. The description adds useful pagination behavior ('Returns one page') but does not disclose additional behaviors like default page size or how filters combine; these are partially covered by the schema.

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 filler: the first sentence lists searchable dimensions, the second gives the one-page behavior and the UUID routing hint. Every clause earns its place and the most decision-relevant information is front-loaded.

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

Completeness4/5

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

Given the output schema, annotations, and self-describing parameter names, the description is nearly sufficient. It clearly communicates scope and the main alternative, though it does not differentiate among the many other CRM contact/list siblings like crm_contacts_by_relationship_list or crm_customers_contacts_list.

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 67%, so the description is not the primary source for parameter meaning. It helps by grouping filters into categories (name, title, reference ID, archive status, date ranges) and gives semantic context to the undocumented date-time parameters, but it does not map them to specific parameter names or describe pagination/sorting controls beyond what the schema already states.

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?

States a specific action ('Search CRM contacts') and enumerates the available filters: name, title, reference ID, archive status, and date ranges. The second sentence distinguishes it from crm_contacts_get, so an agent can immediately tell list/search behavior from single-record retrieval.

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?

Explicitly tells the agent to use crm_contacts_get when a known UUID is available, which is a clear routing rule. 'Returns one page' also implies this is not a bulk-export tool, though other sibling contacts-list variants are not explicitly contrasted.

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

Deploy Server