ServiceTitan MCP

export_employees

Read-onlyIdempotent

Read the incremental employee export feed to synchronize employee data across domains. Use continuation tokens to fetch all changes and include recent uncommitted updates when needed.

Instructions

Read the incremental employee export feed for cross-domain bulk synchronization. This is the same feed as people_employees_export; 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 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.9/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, open-world, and non-destructive. The description adds valuable behavioral context beyond that: it is an incremental feed, has continuation/pagination semantics, requires waiting before re-polling, and includeRecentChanges may produce duplicate records. 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, all dense with useful information. The core purpose is front-loaded, followed by the alias warning and the polling/duplication caveats. No filler or redundancy.

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 tool is an incremental export feed with rich annotations and an output schema. The description covers the essential operational concerns: alias equivalence, polling continuation, waiting behavior, and duplicate-record risk. Nothing critical for correct invocation is missing.

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 meaningful semantic context for includeRecentChanges by warning that it may repeat records, and it explains the continuation flow with continueFrom/hasMore, which complements the 'from' parameter description. It does not fully rewrite param docs, but it improves the agent's operational understanding.

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 states a specific verb ('Read'), a specific resource ('incremental employee export feed'), and its purpose ('cross-domain bulk synchronization'). It also names the sibling alias people_employees_export and clarifies the two are the same feed, so an agent can distinguish it from the many other export_* siblings without opening schemas.

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 explicitly names the alternative (people_employees_export), says to use whichever name is available, and instructs not to fetch both. It also gives concrete polling guidance: continue immediately with continueFrom while hasMore is true, and retain and wait when hasMore is false. This is direct, actionable usage guidance.

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

Deploy Server