Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_bookings_contacts_list

Read-onlyIdempotent

Retrieve contacts attached to a tenant booking by supplying the booking ID. Use page and pageSize to paginate through results.

Instructions

List one page of contacts attached to a tenant booking. Supply the booking ID; use page and pageSize to continue through results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBooking ID
pageNoPage number (starts at 1)
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  2. First observedv2.5.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, covering the safety profile. The description adds pagination semantics ('one page', 'continue through results'), but it does not disclose other behavioral details such as default paging behavior or the effect of includeTotal beyond what the schema already states.

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 states the action and scope, the second gives the two essential pieces of invocation guidance. Information is front-loaded and every clause contributes.

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 simple read-only paginated list with a rich output schema and strong annotations, the description is nearly complete. The main gap is the lack of explicit distinction from the similar crm_bookings_provider_contacts_list sibling, which an agent might confuse without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters. The description adds value by explaining that the booking ID is the required anchor and that page/pageSize drive result continuation, which clarifies their role beyond the raw schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List' and the resource 'contacts attached to a tenant booking', making the core purpose plain. It does not explicitly contrast with the closely named sibling crm_bookings_provider_contacts_list, so it stops short of full sibling differentiation.

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?

The description tells the agent to supply the booking ID and to use page/pageSize for pagination, which is actionable context. It does not explicitly discuss when to choose this tool over sibling contact-list tools, so exclusion guidance is missing.

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

Deploy Server

Other Tools