ServiceTitan MCP

export_membership_status_changes

Read-onlyIdempotent

Fetch incremental membership status changes for synchronized exports, resuming from a date or token and paging with hasMore until all changes are read.

Instructions

Read the incremental membership status changes 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.8/5.0

Behavior5/5

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

The description goes well beyond the readOnly/openWorld/idempotent annotations by explaining feed continuation, polling behavior, and the fact that includeRecentChanges may return records sooner but can repeat them. This is important operational behavior an agent must know to avoid data loss or duplicate processing.

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 tool's purpose, followed by the exact feed-consumption algorithm and a caveat about includeRecentChanges. There is no filler or repetition of structured metadata.

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, the description covers the full lifecycle: initial start, continuation, termination/polling behavior, and optional recent-uncommitted changes. Since an output schema exists, return shape details are already available, so the description is appropriately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema already documents both parameters, the description adds meaningful operational semantics: omitting from starts at the beginning, continuation should use the returned token, and includeRecentChanges trades freshness for possible repeats. The only minor gap is that continueFrom is not explicitly mapped to the schema's from parameter, but the schema's 'continuation token' language makes that inferable.

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 clearly states that this tool reads an incremental export feed of membership status changes for bulk synchronization. The verb 'read' plus the specific resource and intent distinguish it from list-oriented sibling tools such as memberships_status_changes_list.

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 a concrete consumption protocol: start with a date or omit from, continue with continueFrom while hasMore is true, retain the token and wait when false. It does not explicitly name alternative tools for one-off queries, but the bulk-sync context makes the intended usage unambiguous.

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

Deploy Server