ServiceTitan MCP

export_leads

Read-onlyIdempotent

Keep your lead data in sync by reading incremental changes from the export feed, using continuation tokens to resume from the last checkpoint.

Instructions

Read the incremental leads 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.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds substantial behavioral detail beyond those annotations: the incremental feed semantics, token-based continuation, polling cadence, and the repeat-records caveat for includeRecentChanges. This gives an agent a realistic model of how the feed behaves.

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 dense sentences with no filler. The first sentence establishes purpose, the second explains pagination/continuation, and the third warns about duplicate records. Information is front-loaded and each sentence earns its place.

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?

For a feed-based export tool with an output schema and rich annotations, the description covers the essential protocol: how to start, how to continue, when to stop polling, and the repeat-record caveat. An agent has enough context to invoke and iterate correctly without ambiguity.

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 value by explaining the behavioral role of 'from' (start at beginning if omitted) and 'includeRecentChanges' (sooner results but possible duplicates), which goes beyond the schema's basic property descriptions.

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 a specific verb and resource: 'Read the incremental leads export feed for bulk synchronization.' This clearly identifies the tool as a read-only feed for leads and distinguishes it from sibling export feeds like export_customers or export_appointments by naming the entity (leads) and the mode (incremental feed).

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 operational guidance: start with a date or omit from, continue with continueFrom while hasMore is true, retain the token and wait before polling again when hasMore is false, and understand includeRecentChanges trade-offs. It does not explicitly compare against alternatives like crm_leads_list, but the 'bulk synchronization' context makes the intended use clear.

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

Deploy Server