ServiceTitan MCP

export_materials

Read-onlyIdempotent

Synchronize material records by reading the incremental export feed. Start with a date or continuation token, then continue from the provided cursor while hasMore is true.

Instructions

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, but the description adds meaningful behavioral detail: the feed can be started from a date or from the beginning, continuation uses hasMore/continueFrom, and includeRecentChanges may return duplicates. This goes beyond what annotations and the schema alone reveal.

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, front-loaded with the core purpose, explain the full pagination lifecycle without extraneous content. Every sentence contributes operational guidance an agent needs to use the feed correctly.

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 bulk-sync export feed, the description covers initialization, continuation, terminal behavior, and the duplicate risk of includeRecentChanges. Since an output schema exists, the description does not need to enumerate return fields, and the guidance is complete enough to drive correct usage.

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 that 'from' can be omitted to start at the beginning and that includeRecentChanges can cause records to repeat. The only slight weakness is that 'continueFrom' is mentioned without explicitly stating that it should be passed back as the 'from' parameter.

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 materials export feed for bulk synchronization.' It clearly identifies the tool as an export/read operation for materials, and the 'incremental' qualifier distinguishes it from other export_* siblings like export_inventory_bills or export_services.

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 clear operational context for when and how to use this tool: start with a date, omit from for the beginning, continue as long as hasMore is true, and wait before polling when hasMore is false. It does not explicitly exclude alternatives or name sibling tools, but the purpose and pagination protocol make its 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