ServiceTitan MCP

crm_customers_contacts_modified_list

Read-onlyIdempotent

Find contacts for selected customers by created or modified date. Returns paginated results to identify recent additions or updates.

Instructions

Search contact records across specified customers using created or modified time ranges. Returns one page; use crm_customers_contacts_list for all contacts of one known customer.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`pageSize`	No	Records per page (default 50)
`customerIds`	No	Comma-delimited customer IDs
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the description carries less safety burden. It adds useful behavioral context beyond annotations by stating the tool 'Returns one page' and that filtering is based on created or modified time ranges.

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 front-loads the purpose and filter scope, and the second handles pagination and sibling routing. Every clause earns its place.

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?

For a read-only, paginated search tool with annotations, an output schema, and multiple sibling tools, the description is largely complete: it covers scope, time filters, pagination behavior, and the key alternative. The main gap is that it does not explicitly state whether customerIds is required or what happens when omitted, which matters given openWorldHint.

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 coverage is 50%, with good descriptions for page, pageSize, customerIds, and includeTotal, but no descriptions for the four date parameters. The description provides the umbrella concept of 'created or modified time ranges' and 'specified customers', which helps map parameters to intent, but it does not detail per-parameter semantics like the difference between Before and OnOrAfter or combination constraints.

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 opens with a specific verb ('Search') and names the exact resource ('contact records'), with scope ('across specified customers') and key filters ('created or modified time ranges'). It also explicitly distinguishes the closest sibling, crm_customers_contacts_list, by stating that sibling is for all contacts of one known customer.

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 provides an explicit alternative and the condition that selects it: use crm_customers_contacts_list for all contacts of one known customer. This implies the current tool is for cross-customer, time-filtered contact searches, leaving minimal ambiguity about when to choose it.

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

Deploy Server