ServiceTitan MCP

export_purchase_orders

Read-onlyIdempotent

Fetch incremental purchase order records for bulk sync. Start with a date or token, then continue while more data exists; optionally include recent uncommitted changes.

Instructions

Read the incremental purchase orders 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 flag read-only, idempotent, open-world behavior, and the description adds the non-obvious feed mechanics: the hasMore/continueFrom loop, pause-and-poll behavior, and the duplicate/early-return caveat for includeRecentChanges. This is exactly the behavioral context an agent needs beyond the 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 sentences with no filler: purpose first, then the start/continue/termination algorithm, then the important caveat. Every sentence carries operational value.

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?

For a zero-required-parameter incremental feed with an output schema and clear annotations, the description covers how to start, how to page, when to stop, and what caveat to expect. Nothing essential is missing 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 baseline is 3, but the description adds meaning: 'from' can be omitted to start at the beginning, and includeRecentChanges may return records sooner but can repeat them. It does not explicitly map the response's continueFrom value back to the from parameter, but the schema already documents from as a continuation token.

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 purchase orders export feed for bulk synchronization.' It clearly identifies this as the incremental bulk-export variant among many purchase-order and export siblings, so an agent can distinguish it from inventory_purchase_orders_get/list.

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 a clear usage context (bulk synchronization) and concrete polling instructions: start with a date or omit from, continue with continueFrom while hasMore is true, and retain/wait when hasMore is false. It does not explicitly name alternatives or say when not to use the feed, so it falls short of the highest bar.

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

Deploy Server