ServiceTitan MCP

export_installed_equipment

Read-onlyIdempotent

Retrieve an incremental feed of installed equipment for bulk synchronization. Start from a token or date, continue with continuation tokens, and include recent changes when needed.

Instructions

Read the incremental installed 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond that: the feed is incremental, continuation is driven by hasMore, and includeRecentChanges may repeat records. This is meaningful and consistent with 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 concise sentences, each earning its place: purpose, continuation protocol, and includeRecentChanges caveat. The most important usage information is front-loaded.

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?

The complexity is moderate (incremental cursor feed), and the description covers the complete polling lifecycle: initial start, continuation, waiting, and the repeat-record caveat. With an output schema present and annotations covering safety, this is nearly complete; the only minor gap is not clarifying how the response's continueFrom value is passed back into the from parameter.

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 description coverage is 100%, so the baseline is 3. The description adds extra meaning by stating that omitting from starts at the beginning of the feed and that includeRecentChanges trades freshness for possible duplicates. The only slight weakness is using 'continueFrom' without explicitly mapping it back to the from parameter, though schema already identifies 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 installed equipment export feed for bulk synchronization.' It clearly identifies the tool as an incremental export feed for installed equipment, which distinguishes it from the many sibling export_* tools (e.g., export_equipment) and from dispatch_installed_equipment_list/get.

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 an explicit polling protocol: start with a date or omit from to start at the beginning, continue while hasMore is true, wait before polling again when false, and be aware includeRecentChanges returns records sooner but may repeat them. It does not explicitly name alternatives or exclusion conditions, so it falls just 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