ServiceTitan MCP

export_invoice_templates

Read-onlyIdempotent

Fetch incremental invoice template changes for bulk synchronization. Start from a date or feed beginning, follow continuation tokens while hasMore is true, then retain the token, wait, and poll again.

Instructions

Read the incremental invoice templates 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

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description reveals important feed behavior: incremental continuation via hasMore/continueFrom, the need to wait before polling again, and the tradeoff that includeRecentChanges may return records sooner but can repeat them. This is valuable behavioral context an agent could not infer from annotations alone.

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?

The description is compact and front-loaded with its purpose, with no filler. Slight referential ambiguity in 'when false retain it' and the unlinked continueFrom term keep it from being perfectly clear and structured.

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?

Given the output schema exists and annotations cover safety, the description handles the core export lifecycle well: initial start, continuation, polling pause, and duplicate risk. Minor missing details are the explicit continueFrom-to-from mapping and any guidance on polling intervals, but the description is otherwise sufficient for correct invocation.

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 schema already describes both parameters. The description adds meaningful behavior: omitting from starts at the beginning, and includeRecentChanges can cause duplicates. However, it references continueFrom without explicitly mapping it back to the from parameter, leaving a small inference gap.

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 opens with a specific verb and resource: 'Read the incremental invoice templates export feed for bulk synchronization.' This clearly distinguishes it from sibling export feeds like export_invoices or export_invoice_items, and its synchronization purpose is explicit.

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?

The description gives a clear polling protocol: start with a date or omit from, continue with continueFrom while hasMore is true, and wait when hasMore is false. It does not explicitly mention alternatives or exclusions among the many other export tools, so it stops short of a 5, but the context is strong.

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

Deploy Server