ServiceTitan MCP

people_employees_export

Read-onlyIdempotent

Fetch incremental employee data for People synchronization. Use the returned continuation token to keep reading while more data exists, then retain it and wait before polling again.

Instructions

Read the incremental employee export feed for People synchronization. This is the same feed as export_employees; use whichever name is available and do not fetch both. Continue immediately with continueFrom while hasMore is true; when false, retain it and wait before polling again. includeRecentChanges may repeat records.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`from`	No	Continuation token from previous response or custom start date
`includeRecentChanges`	No	Prioritize recent changes in the export stream

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds substantial behavioral context beyond them: the feed is incremental, it shares a source with export_employees (fetching both would duplicate work), records may repeat when includeRecentChanges is set, and the continuation-token polling loop. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, zero filler. The purpose is front-loaded, deduplication guidance comes second, and the polling protocol and caveat close it out. Every sentence carries operational value.

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?

An output schema exists so return-value documentation is not needed, and annotations cover the safety profile. The description covers deduplication, polling, and duplicate-record behavior. Slight gap: the 'continueFrom' vs. 'from' parameter-name mismatch is not reconciled, which could cause an agent to look for a non-existent 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 coverage is 100% (both 'from' and 'includeRecentChanges' have descriptions), so the baseline is 3. The description adds real value beyond the schema by explaining how the token drives the polling loop and by warning that includeRecentChanges may produce duplicate records. Minor deduction for using the term 'continueFrom' when the schema parameter is named 'from' — the mapping is implied but not explicit.

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 opening clause states a specific verb and resource ('Read the incremental employee export feed for People synchronization') and explicitly disambiguates from the near-identical sibling export_employees ('This is the same feed as export_employees'). An agent can distinguish this tool from its 90+ siblings without opening the schema.

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 routing guidance ('use whichever name is available and do not fetch both'), a precise polling protocol ('Continue immediately with continueFrom while hasMore is true; when false, retain it and wait before polling again'), and a behavior caveat ('includeRecentChanges may repeat records'). This is textbook when/how-to-use guidance.

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

Deploy Server