ServiceTitan MCP

export_appointment_assignments

Read-onlyIdempotent

Read the incremental appointment assignments feed to sync bulk data. Continue from a token for subsequent pages, and optionally include recent uncommitted changes.

Instructions

Read the incremental appointment assignments 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.8/5.0

Behavior5/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral detail beyond those: the incremental feed pagination protocol, the hasMore/continueFrom loop, and the caveat that includeRecentChanges can return repeat records. This is valuable context that is not inferable from the annotations or schema.

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 cover purpose, pagination flow, and the includeRecentChanges tradeoff. Each sentence adds non-redundant information, and the most important usage guidance is front-loaded.

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?

Given the output schema exists and the annotations cover safety and idempotency, the description is complete for an incremental export feed tool. It explains the full polling loop, how to start, and the one nuanced behavior that could surprise callers. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description enriches both parameters. It explains how to use 'from' to start at the beginning or resume, and adds the repeat-records caveat for includeRecentChanges that goes beyond the schema's 'include recent changes not yet committed'.

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 'Read the incremental appointment assignments export feed for bulk synchronization', using a specific verb and resource that clearly identifies the tool's purpose. It distinguishes this from sibling export tools by specifying 'appointment assignments' and 'incremental' feed semantics rather than a generic list operation.

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 concrete usage guidance: start with a date or omit 'from', continue with 'continueFrom' while 'hasMore' is true, and retain/wait when false. It does not explicitly name alternative tools or exclusion conditions, but the sequencing and polling context are clear enough for an agent to use it correctly.

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

Deploy Server