ServiceTitan MCP

export_bookings

Read-onlyIdempotent

Read incremental bookings feed for bulk synchronization. Use a date or continuation token to start, then continue from token while more records exist, pausing before polling again.

Instructions

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

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description adds meaningful behavioral context beyond them: the polling and continuation protocol involving hasMore and continueFrom, plus the caveat that includeRecentChanges may return records sooner but can repeat them. This discloses pagination and duplicate behavior that was not visible in structured data.

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 dense sentences, with the purpose front-loaded and the operational protocol in the second sentence. No filler or repetition; every clause contributes to the caller's ability to use the feed correctly.

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 all essential operational aspects: initial start behavior, continuation token usage, polling/waiting semantics, and duplicate behavior of includeRecentChanges. An output schema is present, so return-value details do not need to be in the description. Nothing critical is missing for calling this tool correctly.

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 both parameters. The description enriches both: it explains that omitting 'from' starts at the beginning of the feed, and that includeRecentChanges may return records sooner at the cost of duplicates. This goes beyond the schema descriptions, though the added value is not extensive enough for a 5.

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 uses a specific verb ('Read') and a specific resource ('incremental bookings export feed for bulk synchronization'), which clearly identifies both the operation and its scope. It differentiates from sibling tools like crm_bookings_list or export_appointments by emphasizing the bulk-sync export-feed nature, making the intended use unambiguous.

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 detailed, actionable usage guidance: start with a date or omit it, continue with continueFrom while hasMore is true, and wait before polling once hasMore is false. It clearly states the context ('for bulk synchronization') but does not explicitly name alternatives or exclusion conditions, stopping short of a full 5.

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

Deploy Server