ServiceTitan MCP

export_equipment

Read-onlyIdempotent

Read the incremental equipment export feed to sync equipment changes in bulk. Begin at a date or the start of the feed, continue with returned tokens while more records exist, then poll again later for new updates.

Instructions

Read the incremental equipment 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?

Annotations already mark this as read-only, open-world, and idempotent. The description goes well beyond that by explaining the incremental feed mechanics: continuation tokens, hasMore polling behavior, waiting before re-polling, and the duplicate risk introduced by includeRecentChanges. No contradiction with annotations.

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 dense and front-loaded with the core purpose, and every clause earns its place. It is somewhat run-on, packing multiple protocol steps into one long sentence, but it remains appropriately sized for the complexity.

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 rich annotations, full schema coverage, and presence of an output schema, the description covers the essential behavioral loop for calling the tool correctly. The only notable gap is the lack of explicit guidance distinguishing this feed from export_installed_equipment, which could matter during tool selection.

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 documents both parameters. The description adds valuable semantic detail: from can be a date or omitted to start at the beginning, includeRecentChanges returns records sooner but may repeat them, and continueFrom should be fed back into the next call. Minor ambiguity remains around the relationship between the output continueFrom token and the from parameter.

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?

The description clearly states a specific action ('Read the incremental equipment export feed') and its intended purpose ('bulk synchronization'). It is distinct enough to identify the resource, but the sibling list includes export_installed_equipment, and the description does not explicitly differentiate between equipment and installed equipment.

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 provides a concrete usage protocol: start with a date or omit from, continue using continueFrom while hasMore is true, retain the token and wait when false, and warns about includeRecentChanges behavior. However, it does not explicitly state when to choose this tool over other export_* alternatives.

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

Deploy Server