ServiceTitan MCP

export_invoice_items

Read-onlyIdempotent

Retrieve incremental invoice item changes for bulk sync. Start from a date or token, continue with hasMore, and optionally include recent uncommitted records.

Instructions

Read the incremental invoice items 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.7/5.0

Behavior5/5

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

Annotations already mark this readOnly, idempotent, and non-destructive; the description adds valuable feed-specific behavior: continuation semantics, hasMore polling, retaining the cursor, and the repeat-risk of includeRecentChanges. This gives an agent more than the annotation labels alone could convey.

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, all dense with operational guidance and no filler. The most important fact (read feed for bulk sync) is front-loaded, followed by the polling lifecycle.

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?

The description provides the full consumption loop for an incremental export feed: start, continue, poll, and handle recent changes. Combined with readOnly/idempotent annotations and the presence of an output schema for return fields, an agent has enough to call and drive this feed correctly.

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 description is bonus, and it adds meaning: 'from' can be a date or token and can be omitted to start at the beginning; includeRecentChanges may return records sooner but duplicates them. The only minor wrinkle is that continueFrom is referenced but not defined in the input schema, likely an output cursor.

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?

Description opens with a specific verb ('Read'), a precise resource ('incremental invoice items export feed'), and a purpose ('for bulk synchronization'). The 'invoice items' scope distinguishes it from sibling export feeds such as export_invoices and export_invoice_templates.

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?

Provides a clear context for use (bulk synchronization) and a detailed polling/continuation protocol: start from a date or omit from, follow hasMore, retain continueFrom when done, and handle repeatable recent changes. It does not explicitly name alternative tools or give when-not-to-use conditions, 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