ServiceTitan MCP

export_adjustments

Read-onlyIdempotent

Retrieve incremental adjustments for bulk sync using a start date or continuation token. Continue polling with hasMore and continueFrom until false; includeRecentChanges may yield uncommitted duplicates.

Instructions

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

The description reveals meaningful behavior beyond the readOnly/idempotent annotations: the feed must be polled with continuation tokens, hasMore=false means retain the token and wait, and includeRecentChanges may cause duplicate records. This is valuable operational context for an agent.

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?

Two dense sentences with the primary purpose front-loaded and no filler. The phrasing around 'continueFrom' is slightly ambiguous because the input schema only lists 'from', which prevents a perfect score.

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?

With an output schema, read-only annotations, and no required parameters, the description covers the essential sync loop: start position, pagination, polling cadence, and duplicate-risk behavior. The missing explicit link between continueFrom and the from parameter is the main gap.

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. The description adds useful semantics: 'from' can be a date or omitted to start at the beginning, and includeRecentChanges may return records sooner but repeat them. It does not fully clarify how the returned continueFrom maps to 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 opens with a specific verb and resource: 'Read the incremental adjustments export feed for bulk synchronization.' This clearly states what the tool does, though it does not explicitly distinguish itself from sibling tools like export_payroll_adjustments.

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?

Clear procedural context is provided: start with a date or omit 'from', follow continueFrom/hasMore for pagination, and wait before repolling after the feed is exhausted. Alternatives and exclusions are not named, so it stops 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