ServiceTitan MCP

estimates_export_estimates

Read-onlyIdempotent

Export incremental estimate changes from a start date or continuation token to synchronize external systems.

Instructions

Read the incremental estimate export feed for synchronization. Supply from as the change-window start and continue with the response continuation token when present; use estimates_list for interactive filtered browsing and estimates_get for a known ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`from`	No	Continuation token or custom date to begin export
`includeRecentChanges`	No	Include recent changes (may include duplicates)

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

Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), so the description's job is lighter. It adds useful behavioral context by describing the tool as an incremental feed intended for synchronization and by explaining the continuation-token pagination pattern. This goes beyond what the annotations alone provide, though it does not detail output format or edge cases like missing 'from'.

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?

Two sentences with no filler. The primary purpose is front-loaded, and the continuation-token mechanics and sibling alternatives are packed into the second sentence. Every clause earns its place.

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 a read-only export tool: it covers the sync use case, pagination continuation, and how it differs from related estimate tools. The output schema exists, so return-value details are not required. No critical missing context is apparent.

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 value by explaining that 'from' serves as the change-window start and that the response continuation token should be fed back into it—clarifying the incremental feed workflow. It does not add much for includeRecentChanges, but the schema already explains that parameter.

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 estimate export feed for synchronization.' It clearly identifies what the tool does and differentiates it from estimates_list and estimates_get by naming them explicitly. An agent can immediately understand this is the sync/export tool, not the interactive browsing or single-record lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage direction: supply 'from' as the change-window start and continue with the response continuation token when present. It also names the alternatives and their use cases—estimates_list for interactive filtered browsing and estimates_get for a known ID—so an agent knows when not to use this tool.

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

Deploy Server