ServiceTitan MCP

export_business_units

Read-onlyIdempotent

Retrieve changed business units from an incremental export feed for bulk synchronization. Start with a date or continuation token, then keep following the returned token until all changes are fully read.

Instructions

Read the incremental business units 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?

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds meaningful protocol details beyond annotations: continuation tokens, hasMore semantics, polling guidance, and the possibility of repeated records when includeRecentChanges is used. No contradiction with annotations.

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 compact, front-loaded with purpose, and every sentence carries operational value. It avoids fluff and presents the start/continue/polling sequence in a logical order.

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?

With an output schema present, the description does not need to enumerate return fields. It covers the essential protocol for correct incremental synchronization, including how to start, continue, stop, and handle eventual consistency. This is complete for a feed-reading tool.

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?

Schema coverage is 100%, but the description adds valuable nuance beyond the schema: 'from' can be omitted to start at the beginning of the feed, and includeRecentChanges may return records sooner but can repeat them. This directly helps an agent decide how to set each parameter.

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 and resource: 'Read the incremental business units export feed for bulk synchronization.' It clearly distinguishes this tool from the many export_* siblings by identifying the resource and the incremental-feed nature, so an agent can select it correctly.

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 context: start with a date or omit from, continue with continueFrom while hasMore is true, wait before polling after hasMore is false, and understand includeRecentChanges caveats. It does not explicitly name alternative tools, but the usage protocol is sufficiently clear for this feed endpoint.

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

Deploy Server