ServiceTitan MCP

export_invoices

Read-onlyIdempotent

Sync invoices in bulk by reading the incremental export feed. Begin from a date or continuation token, then continue with continueFrom while more records exist.

Instructions

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

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld/destructive annotations, it discloses non-obvious feed behavior: continuation tokens, hasMore polling, waiting when the feed is exhausted, and possible duplicate records with includeRecentChanges. This materially helps an agent reason about repeated calls.

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 front-load the purpose and avoid fluff. The middle sentence is a long run-on and parameter names aren't formatted (e.g., from, continueFrom), which makes the polling instruction slightly harder to parse than necessary.

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 paginated incremental feed, it covers the full call lifecycle and duplicate behavior, and output schema/annotations fill in the rest. A more complete description would explicitly say to pass the returned continueFrom value as the from argument on subsequent requests.

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%, and the description adds real usage meaning: omitting from starts at the beginning, includeRecentChanges trades recency for duplicates. The slight ambiguity is that continueFrom is described as something to continue with but the description never explicitly maps it to the from parameter on the next call.

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?

Description clearly identifies the tool as reading the incremental invoices export feed for bulk synchronization, with a specific verb, resource, and use case. It does not explicitly contrast itself with any sibling export/list endpoint, so it stops short of full 5.

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 context and operational steps: start with a date or omit the from parameter, follow hasMore/continueFrom, and wait before polling again. It doesn't state when not to use this tool or name an alternative, which keeps it at 4.

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

Deploy Server