ServiceTitan MCP

export_activity_codes

Read-onlyIdempotent

Fetch incremental activity-code updates for cross-domain bulk synchronization. Continue with the provided token while more records exist, then wait before polling again.

Instructions

Read the incremental activity-code export feed for cross-domain bulk synchronization. This is the same feed as settings_activity_codes_export; use whichever name is available and do not fetch both. Continue immediately with continueFrom while hasMore is true; when false, retain it and wait before polling again. includeRecentChanges may repeat records.

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?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses incremental-feed behavior, continuation/pagination semantics, the need to wait after hasMore is false, and the fact that includeRecentChanges may produce duplicate records. No contradiction with annotations exists.

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?

Four short sentences, each carrying a distinct piece of information: purpose, sibling alias, pagination protocol, and parameter caveat. The core action is front-loaded and no sentence is wasted.

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 read-only, incremental export tool with an output schema and no required parameters, this description covers purpose, alias avoidance, pagination loop behavior, and duplicate caveat. Nothing essential for correctly invoking and consuming the feed 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 covers both parameters with 100% description coverage, so the baseline is 3. The description adds value by warning that includeRecentChanges may repeat records, connecting that parameter to a behavioral consequence not stated in 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?

Description opens with a specific verb-resource pair ('Read the incremental activity-code export feed') and its purpose ('cross-domain bulk synchronization'), immediately distinguishing this from the many other export_* siblings. It also names the exact sibling alias (settings_activity_codes_export) and states they expose the same feed.

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?

Explicitly says the tool is interchangeable with settings_activity_codes_export and instructs the agent to use whichever name is available and not fetch both. It also provides concrete polling direction: continue immediately while hasMore is true, otherwise retain the token and wait before polling again.

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

Deploy Server