ServiceTitan MCP

export_appointments

Read-onlyIdempotent

Pull incremental appointment updates for bulk sync. Use the continuation token to iterate through all changes, then pause before polling again.

Instructions

Read the incremental appointments 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.3/5.0

Behavior4/5

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

The description reveals important behavior beyond the readOnly/openWorld/idempotent annotations: the cursor-based continuation with 'hasMore', the need to wait before polling again, and that 'includeRecentChanges' may return duplicate records. This is valuable contextual transparency, though it leaves some details such as exact return shape to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the tool's purpose, and each sentence adds necessary protocol detail. It is moderately dense with useful information, though the nested polling instructions could be slightly clearer; there is no wasted text.

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?

Given the output schema and annotations exist, the description sufficiently covers the main operational behaviors: starting the feed, continuing with the cursor, stopping and waiting, and handling uncommitted changes. It could be more explicit about passing the returned continuation token back into 'from', but overall the tool is well contextualized for an incremental export.

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?

The schema already documents both parameters, so baseline is 3. The description adds useful meaning: 'from' can be a date or omitted to start at the beginning, and 'includeRecentChanges' may return records sooner but with possible repeats. However, it references 'continueFrom' without explicitly showing it maps to the 'from' parameter, which is a minor clarity gap.

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 clearly states the tool 'Read[s] the incremental appointments export feed for bulk synchronization,' which identifies the specific verb, resource, and purpose. This distinguishes it from sibling tools like export_appointment_assignments or dispatch_appointments_list by emphasizing the incremental feed for bulk sync.

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 provides a clear usage protocol: start with a date or omit 'from', continue while 'hasMore' is true, and wait when it becomes false. It does not explicitly name alternative tools or when-not-to-use cases, but the bulk-synchronization context and incremental-feed mechanics are clear enough.

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

Deploy Server