ServiceTitan MCP

export_inventory_bills

Read-onlyIdempotent

Fetch incremental inventory bills from the export feed for bulk synchronization. Start from a date or continuation token, page through results with continueFrom while hasMore is true, and optionally include recent uncommitted changes.

Instructions

Read the incremental inventory bills 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.8/5.0

Behavior5/5

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

The description adds meaningful behavior beyond the annotations by explaining the incremental feed semantics: hasMore/continueFrom continuation, the need to retain the token when hasMore is false, and the risk of repeated records when includeRecentChanges is used. This goes well beyond the readOnly/idempotent annotations.

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 cover the essential feed protocol without wasted words. The most important action (read the feed for synchronization) is front-loaded, and the parameter semantics are explained compactly.

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 is complete for an incremental export feed: it explains starting, continuing, polling, and the trade-off of includeRecentChanges. The output schema is present, so the description does not need to enumerate return fields, and the annotations cover safety and idempotency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds important behavioral meaning to the parameters: 'from' can be a date or continuation token and can be omitted to start at the beginning, and 'includeRecentChanges' trades off sooner records against possible duplicates. This materially helps correct invocation.

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 a specific verb ('Read'), a specific resource ('incremental inventory bills export feed'), and a clear purpose ('bulk synchronization'). This makes it easy to distinguish from the many sibling export_* feed tools.

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 usage guidance for the feed protocol: how to start, when to continue, when to retain the continuation token, and when to wait before polling again. It does not explicitly discuss alternatives or exclusions, but the resource is distinct among siblings.

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

Deploy Server