Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_payroll_adjustments

Read-onlyIdempotent

Pull incremental payroll adjustment records for bulk synchronization, starting from a date or continuation token and paging with continueFrom while hasMore remains true.

Instructions

Read the incremental payroll adjustments 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
NameRequiredDescriptionDefault
fromNoContinuation token or date string for incremental export
includeRecentChangesNoInclude recent changes not yet committed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • removedInput schema / properties / modifiedBefore
      Removed value: -{
-  "description": "Filter: modified before this date (ISO 8601)",
-  "type": "string"
-}
    • removedInput schema / properties / modifiedOnOrAfter
      Removed value: -{
-  "description": "Filter: modified on or after this date (ISO 8601)",
-  "type": "string"
-}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  2. First observedv2.5.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds substantial behavioral context beyond that: the continuation token protocol, hasMore semantics, the need to wait before re-polling, and the fact that includeRecentChanges may return duplicate records. This is rich and non-obvious behavior clearly disclosed.

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?

The description is two dense sentences with no filler. It front-loads the core purpose, then immediately provides the essential polling algorithm and caveat. Every 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 an incremental export feed tool with annotations and an output schema, the description covers the full lifecycle: how to start, how to continue, how to know when to stop, and when to poll again. The includeRecentChanges caveat is also disclosed. Nothing essential 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?

The input schema already describes both parameters with 100% coverage, giving a baseline of 3. The description adds meaningful semantics by explaining how to use 'from' as a starting point or omit it, and by clarifying that includeRecentChanges returns records sooner but may repeat them. This goes beyond the schema descriptions.

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 clearly states a specific verb ('Read'), a specific resource ('incremental payroll adjustments export feed'), and the purpose ('bulk synchronization'). It distinguishes itself from ordinary list/get endpoints by emphasizing the incremental feed nature, though it does not explicitly call out sibling alternatives like export_adjustments.

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, actionable usage guidance: start with a date or omit it, continue with continueFrom while hasMore is true, and retain the token when false before polling again. It also explains the tradeoff of includeRecentChanges. However, it does not explicitly mention when not to use this tool or name alternative tools.

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

Deploy Server

Other Tools