ServiceTitan MCP

crm_customers_contacts_list

Read-onlyIdempotent

Retrieve a paginated list of contacts attached to a known customer by providing its ID. Control results with page and page size options.

Instructions

List one page of contacts attached to a known customer. Use crm_customers_contacts_modified_list for cross-customer incremental contact queries.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Customer ID
`page`	No	Page number (starts at 1)
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response

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 declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds meaningful behavioral context by specifying that only one page is returned and that results are scoped to a single customer, which is beyond what annotations or schema alone communicate. It does not contradict any annotation.

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 wasted words. The primary purpose is front-loaded, and the alternative tool reference is included succinctly in the second sentence. Every word 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?

For a simple paginated list endpoint, the description fully covers what an agent needs to know: the resource scope, pagination behavior, and the routing decision between this and the sibling tool. With an output schema present and annotations covering safety traits, nothing essential is missing.

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 100%, with all four parameters having clear descriptions (id, page, pageSize, includeTotal). The description's 'one page' phrase lightly reinforces pagination but adds no significant meaning beyond the schema. Per the baseline rule, a 3 is appropriate when the schema already documents parameters thoroughly.

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 verb ('List'), a specific resource ('contacts attached to a known customer'), and explicitly differentiates from the sibling tool 'crm_customers_contacts_modified_list'. It clearly indicates pagination with 'one page', making the tool's scope immediately understandable.

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 tells the agent when to use this tool: to list a page of contacts for a known customer. It also explicitly names the alternative for cross-customer incremental queries, giving a clear exclusion condition. This is direct, actionable guidance with no ambiguity.

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

Deploy Server