ServiceTitan MCP

export_locations_contacts

Read-onlyIdempotent

Read incremental location contacts export for bulk sync. Start from a date or token, continue with hasMore, and include recent changes to avoid missing updates.

Instructions

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

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses key feed behaviors: incremental continuation via continueFrom/hasMore, the need to retain the token when the feed is exhausted, and the risk that includeRecentChanges returns records that may repeat. This materially helps an agent predict response behavior without calling the tool.

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?

Three dense sentences front-load the tool's purpose then deliver the continuation algorithm and a warning about includeRecentChanges. No filler is present and the structure matches the order an agent needs: what, how to start, how to continue, edge-case behavior.

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?

For a read-only feed tool with an output schema present, the description covers the only non-schema behavior an agent needs: initialization, continuation, termination, and the includeRecentChanges caveat. Nothing essential about calling the tool correctly is left ambiguous.

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 already 100%, and the description adds useful semantics beyond the schema: omitting from starts at the beginning, and includeRecentChanges may return data sooner but with possible duplicates. This goes beyond the schema's 'Continuation token or date string' and 'not yet committed' wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb, resource, and use case: 'Read the incremental locations contacts export feed for bulk synchronization.' It clearly conveys what the tool does, though it does not explicitly contrast it with sibling export feeds such as export_locations or export_customers_contacts.

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 provides concrete operational guidance: start with a date or omit from for the beginning, follow continueFrom while hasMore is true, and stop polling when hasMore is false. It does not name alternative tools, but the when-to-use is clear from the bulk synchronization context and feed semantics.

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

Deploy Server