Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

export_customers_contacts

Read-onlyIdempotent

Read the incremental customer contacts feed to sync bulk changes. Start with a date, then follow continuation tokens until hasMore is false, polling when complete.

Instructions

Read the incremental customers contacts 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. Changed1 schema field changedv3.0.0
    • 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.3/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, open-world, and non-destructive. The description adds genuinely useful behavioral context: feed continuation semantics, the `hasMore` polling loop, and the duplicate-record caveat for `includeRecentChanges`. It omits rate-limit specifics, but the annotations lower the burden here.

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 dense and front-loaded with purpose, and every sentence contributes. The continuation/polling clause is slightly run-on and uses 'it' a bit vaguely, but the overall structure is efficient for the amount of protocol it conveys.

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?

With an output schema present and full parameter schema coverage, the description does not need to enumerate return fields. It covers initialization, pagination, polling, and the `includeRecentChanges` caveat. The missing explicit connection between the returned `continueFrom` and the `from` parameter is the main completeness gap.

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?

Since the schema already documents both parameters, the baseline is 3. The description adds value by explaining the default behavior when `from` is omitted and warning that `includeRecentChanges` may repeat records. There is slight ambiguity because the returned `continueFrom` is not explicitly mapped to the `from` parameter for the next call.

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 first sentence identifies a specific verb ('Read'), a specific resource ('incremental customers contacts export feed'), and the intended use case ('bulk synchronization'). This is strong enough to distinguish it from direct CRM list/read endpoints and from other export feeds by the customers-contacts scope and incremental-feed nature.

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 an explicit usage protocol: start by providing a date or omitting `from`, continue while `hasMore` is true, retain the token and wait when false, and it explains the trade-off of `includeRecentChanges`. It does not name alternatives or exclusion cases, so it stops short of a 5.

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