ServiceTitan MCP

export_technicians

Read-onlyIdempotent

Fetch incremental technician exports for bulk synchronization, continuing from a token or start date while tracking hasMore to avoid missing records.

Instructions

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds valuable stateful semantics about incremental feeds: continuation tokens, immediate polling while hasMore is true, waiting when false, and possible repeated records with includeRecentChanges. This goes well beyond the annotations and clearly describes the tool's behavioral contract.

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?

The description is compact and front-loaded, with three sentences covering purpose, invocation sequence, and a caveat. Minor phrasing ambiguities, such as 'omit from' and 'when false retain it', prevent it from being perfectly clear and earning a 5.

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?

The description covers the full lifecycle of consuming an incremental feed: start, continue, pause/wait, and the effect of includeRecentChanges. An output schema exists, so return fields need not be enumerated, but the description does not explicitly state that the returned continueFrom should be passed back as the 'from' 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%, so the baseline is 3; the description adds extra meaning by explaining that omitting 'from' starts at the beginning and that includeRecentChanges may return records sooner but can repeat them. However, it references 'continueFrom' as if it were a parameter, while the schema only exposes 'from', making the token-to-parameter mapping slightly ambiguous.

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 states a specific action ('Read'), resource ('technicians export feed'), and purpose ('bulk synchronization'), making the tool's function clear. It does not explicitly contrast itself with sibling tools like export_employees or people_employees_export, so it lacks explicit sibling differentiation.

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?

Provides clear operational guidance: start with a date or omit 'from', continue with the token while hasMore is true, retain and wait when hasMore is false, and understand that includeRecentChanges can return duplicates. It does not mention alternative tools or exclusion conditions, but the use case is well contextualized.

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

Deploy Server