ServiceTitan MCP

export_activities

Read-onlyIdempotent

Retrieve incremental timesheet-activity records for cross-domain bulk synchronization. Use with a continuation token to process changes in batches, retaining the token when no more records remain.

Instructions

Read the incremental timesheet-activity export feed for cross-domain bulk synchronization. This is the same feed as settings_activities_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?

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: duplicate feed warning, incremental synchronization semantics, continuation/polling behavior, and the fact that includeRecentChanges may repeat records. No contradiction with annotations.

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 sentences carry purpose, alias handling, pagination behavior, polling cadence, and deduplication caveat. Nothing is wasted and the most important scoping information is front-loaded.

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 export feed with an output schema and strong annotations, the description covers all non-obvious operational details: duplicate endpoint, continuation token usage, hasMore handling, and record repetition. The agent has everything needed to call and consume the 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 value by explaining that includeRecentChanges may repeat records and by describing the continuation loop. There is a minor ambiguity where 'continueFrom' is not the actual parameter name ('from' is), but the schema's own description of 'from' as a continuation token largely resolves this.

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 opens with a specific verb and resource: 'Read the incremental timesheet-activity export feed for cross-domain bulk synchronization.' It also explicitly identifies itself as the same feed as settings_activities_export, removing any ambiguity among the large sibling export toolset.

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?

It gives explicit alternative guidance: 'use whichever name is available and do not fetch both.' It also provides a concrete polling and continuation protocol with continueFrom and hasMore, telling the agent exactly how to drive the feed.

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

Deploy Server