ServiceTitan MCP

export_returns

Read-onlyIdempotent

Pull incremental returns data for bulk synchronization. Begin with a date or token, then continue paging until the feed is complete for reliable syncing.

Instructions

Read the incremental returns 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 the feed's incremental behavior, the continuation protocol, and the important caveat that includeRecentChanges may return records sooner but can repeat them. This is exactly the kind of behavioral context an agent needs to avoid polling mistakes and handle duplicates.

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 compact sentences cover purpose, startup, continuation, backoff, and duplicate behavior with no filler. The most important action ('Start with a date or omit from') is front-loaded, and every sentence earns its place.

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?

Given the output schema and annotations are available, the description provides everything needed to drive the incremental loop correctly: initial state, continuation condition, waiting behavior, and the duplicate-risk caveat. It is complete for a bulk synchronization feed tool of this complexity.

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?

With 100% schema coverage, the baseline is 3, but the description adds real value by explaining how to initialize from, how to continue using the feed token, and what includeRecentChanges trades off. The only weakness is that 'continueFrom' is mentioned without explicitly stating that its returned value should be passed back as the from parameter, which could confuse an agent at first read.

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 opens with a specific verb and resource: 'Read the incremental returns export feed for bulk synchronization.' This clearly identifies the tool as a bulk-export reader for returns and distinguishes it from the many other export_* siblings by domain. It could be slightly stronger if it named an alternative or said whether this covers inventory returns rather than financial returns, but the core purpose is 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?

It gives explicit operational guidance: start with a date or omit from to begin at the start, follow continueFrom while hasMore is true, and retain the token and wait before polling again when hasMore is false. This clearly conveys the polling/continuation context. It does not explicitly state when not to use this tool or mention a sibling alternative, so it stops short of a 5.

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

Deploy Server