ServiceTitan MCP

export_gross_pay_items

Read-onlyIdempotent

Retrieve incremental gross pay items export feed for bulk synchronization. Use a continuation token to page through updates, and optionally include recent uncommitted changes.

Instructions

Read the incremental gross pay items 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.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, open-world, and idempotent. The description adds valuable behavioral details beyond that: the feed's continuation mechanism, the `hasMore` flag, the need to retain the token, and the repeat-record tradeoff of `includeRecentChanges`. This is exactly the kind of runtime behavior an agent needs to know.

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. Key information is front-loaded: what the tool is for, how to begin, how to continue, and the caveat about recent changes. Every sentence provides actionable guidance.

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?

Given the annotations and the presence of an output schema, the description covers the full call pattern: starting, iterating, polling, and handling repeatable records. Nothing critical is missing for an agent to invoke and consume this incremental export feed correctly.

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 operational meaning by explaining that `from` can be a date or omitted to start at the beginning of the feed, and clarifies the behavioral tradeoff of `includeRecentChanges`. It also introduces `continueFrom`/`hasMore` context that helps interpret the response, going beyond the schema.

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 action ('Read the incremental gross pay items export feed') and names its purpose ('for bulk synchronization'). This clearly differentiates it from sibling tools like payroll_gross_pay_items_list by indicating it is an incremental feed rather than a plain list.

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?

Provides a concrete polling protocol: start with a date or omit `from`, continue with `continueFrom` while `hasMore` is true, retain the token and wait when false. It also warns about `includeRecentChanges` returning repeated records, giving the agent actionable guidance on how to use the feed correctly.

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

Deploy Server