ServiceTitan MCP

export_customers

Read-onlyIdempotent

Retrieve incremental customer changes for bulk synchronization. Use continuation tokens to page through the feed; include recent changes for sooner results, accepting duplicates.

Instructions

Read the incremental customers export feed for bulk synchronization. Start with a date or omit from to start at the beginning of the feed, continue immediately with continueFrom while hasMore is true, and when false retain it and wait before polling again. includeRecentChanges may return records sooner but can repeat them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`from`	No	Continuation token or date string for incremental export
`includeRecentChanges`	No	Include recent changes not yet committed

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.8/5.0

Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses important feed behavior: records may be repeated when includeRecentChanges is used, and polling should pause when hasMore is false. This gives the agent accurate expectations about duplicate data and pacing.

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?

The description is three focused sentences with no filler. It front-loads the purpose, then gives a compact but complete usage algorithm, and closes with a caveat about duplicate records. Every sentence 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?

Given the low parameter count and the presence of an output schema, the description covers the essential operational details: how to start, how to continue, when to stop, and a known data-quality caveat. Nothing critical is missing for an agent to invoke this tool correctly.

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

Parameters5/5

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

The schema already documents both parameters, but the description adds valuable semantics: 'from' is explained as a starting point with an optional date or continuation token, and continueFrom/hasMore behavior is tied to the pagination flow. The includeRecentChanges caveat about repeats goes well beyond the schema's 'Include recent changes not yet committed.'

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 and resource: 'Read the incremental customers export feed for bulk synchronization.' It clearly identifies this as an incremental export tool for customers, which distinguishes it from sibling export tools like export_customers_contacts and from query-style tools like crm_customers_list.

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 gives clear operational guidance: start with a date or omit from, follow continueFrom while hasMore is true, and wait before polling again when hasMore is false. It does not explicitly name alternative tools or exclusion conditions, but the context of incremental bulk synchronization makes the intended use clear.

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

Deploy Server