ServiceTitan MCP

crm_contacts_by_relationship_list

Read-onlyIdempotent

Search contacts by relationship ID with optional filters for name, title, archive, and date ranges. Get a paginated list of matching contacts.

Instructions

Search contact records associated with a known relationship ID, with optional identity, archive, and date filters. Returns one page; use crm_contact_relationships_list to inspect the links owned by one known contact.

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
`relationshipId`	Yes	Contact relationship ID
`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, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations by stating that the tool 'returns one page' and by framing the search as scoped to a relationship ID, reinforcing the openWorldHint.

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 main operation and scoping are front-loaded, and the sibling alternative is placed second, giving the agent the core decision information immediately.

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?

The tool has 13 parameters, an output schema, and strong annotations, so the description does not need to explain return values or safety. It covers the essential usage context and points to the relevant sibling for relationship-link inspection, leaving only minor gaps such as how to obtain a valid relationshipId in the first place.

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 69%, so most parameters are already documented. The description groups filters into 'identity, archive, and date filters,' which adds some conceptual structure but no new per-parameter meaning beyond what the schema provides, especially for the undocumented date-time parameters.

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 ('Search'), resource ('contact records'), and required context ('known relationship ID'), and lists filter categories. It also explicitly distinguishes itself from crm_contact_relationships_list, so an agent can tell the two sibling tools apart without opening schemas.

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?

It clearly says to use this tool when searching contacts by relationship ID, and explicitly directs agents to crm_contact_relationships_list when the goal is to inspect links owned by one known contact. This is an explicit when/alternative distinction.

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

Deploy Server