ServiceTitan MCP

crm_contact_relationships_list

Read-onlyIdempotent

Retrieve a paginated list of contact-to-entity relationships for a known contact ID. Filter by relationship type, related entity, or creation time to find specific associations.

Instructions

List one page of contact-to-entity relationship records for a known contact UUID, optionally filtered by related entity, type slug, type name, or creation time. Use crm_contacts_by_relationship_list for contacts associated with a known relationship ID.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`pageSize`	No	Records per page (default 50)
`typeName`	No	Relationship type name filter
`typeSlug`	No	Relationship type slug filter
`contactId`	Yes	Contact ID
`includeTotal`	No	Include total count in response
`createdBefore`	No	List relationships created before this timestamp
`relatedEntityId`	No	Related entity ID filter
`createdOnOrAfter`	No	List relationships created on/after this 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. The description adds useful behavior beyond those flags by clarifying the result is a single page and that filtering by related entity, type slug, type name, or creation time is supported. This helps the agent set expectations about pagination and scope.

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 efficient sentences with no filler; the core action and filters are front-loaded, and the alternative tool is mentioned at the end. Every sentence carries useful routing or scoping information.

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?

The description covers purpose, page semantics, optional filters, required contact context, and the inverse sibling tool. With output schema and full parameter descriptions available, nothing essential to correctly invoke this tool 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 coverage is 100%, so the schema documents all 10 parameters. The description adds only a high-level grouping of filters (related entity, type slug, type name, creation time) rather than new format or syntax details, matching the baseline for fully covered schemas.

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?

Description opens with a specific action ('List one page...') and names the exact resource ('contact-to-entity relationship records') plus the required context ('known contact UUID'). It also differentiates from the inverse sibling crm_contacts_by_relationship_list, so an agent can distinguish the tool without inspecting 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?

Explicitly states the primary use case: listing relationship records for a known contact UUID, with optional filters. It also names the alternative crm_contacts_by_relationship_list for the reverse lookup, giving clear when-to-use and when-not-to-use guidance.

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

Deploy Server