ServiceTitan MCP

export_payments

Read-onlyIdempotent

Retrieve incremental payment changes for bulk synchronization. Pass a date or continuation token to start or resume the feed, and poll again only after hasMore returns false.

Instructions

Read the incremental payments 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

Behavior4/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses incremental-feed behavior, continuation via continueFrom/hasMore, polling discipline, and the fact that includeRecentChanges may return duplicate records. The only weakness is not mapping continueFrom explicitly back to the from parameter.

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 sentences front-load the purpose and then pack the necessary iteration/polling protocol without extra filler. Every sentence contributes to correct invocation.

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, idempotent incremental feed with an output schema and only two documented parameters, the description covers start, continuation, polling, and duplicate-repetition semantics. Nothing essential is missing.

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?

Input schema already covers both params (100% coverage), but the description adds operational value: omitting from starts at the beginning, and includeRecentChanges trades recency for possible duplicates. Minor ambiguity: 'continue immediately with continueFrom' refers to a term not in the schema rather than explicitly saying to pass it as from.

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 names the specific resource ('payments export feed') and the intended use ('bulk synchronization'), and uses the verb 'Read'. This clearly distinguishes it from the large family of sibling export_* tools by resource and feed semantics.

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 gives explicit protocol: start with a date or omit from to begin at feed start, continue while hasMore is true, retain the token and wait before polling when false. It establishes when to use the tool (bulk synchronization) but doesn't mention alternatives or when not to use it.

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

Deploy Server