ServiceTitan MCP

export_locations

Read-onlyIdempotent

Fetch incremental location changes for bulk synchronization. Begin with a date or token, then continue with returned continuation values until hasMore is false to keep records in sync.

Instructions

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

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the feed protocol (hasMore, continuation token) and the repeat-records caveat for includeRecentChanges. These are non-obvious behaviors an agent needs to know to synchronize correctly.

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?

Three dense sentences with no filler, and the feed semantics are front-loaded. Minor grammatical awkwardness ('omit from to start') and the undefined-in-schema 'continueFrom' wording keep it from a perfect score.

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 low-complexity read tool with an output schema and safety annotations, the description covers the end-to-end polling loop. It would be more complete with an explicit statement of how 'continueFrom' maps to the 'from' parameter, though the schema partially covers that.

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 defines 'from' and 'includeRecentChanges'. The description adds operational meaning: 'from' can be a date or omitted for feed start, and includeRecentChanges trades up-to-dateness for possible duplicates.

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 ('Read') and a precise resource ('incremental locations export feed'), and states the intended use case ('bulk synchronization'). This clearly distinguishes it from the many sibling export_* tools by naming the location entity and its incremental-feed nature.

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?

It clearly explains how to paginate the feed: start with a date or omit 'from', continue with 'continueFrom' while 'hasMore' is true, and retain/wait when false. It does not explicitly name alternative tools or exclusion conditions, but it gives enough context for the bulk-sync scenario.

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

Deploy Server