ServiceTitan MCP

settings_activities_export

Read-onlyIdempotent

Retrieve incremental timesheet-activity exports for Settings workflows. Use continuation tokens to page through changes, then retain the token and wait before polling again.

Instructions

Read the incremental timesheet-activity export feed for Settings workflows. This is the same feed as export_activities; 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 from previous response or custom start date
`includeRecentChanges`	No	Prioritize recent changes in the export stream

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, open-world, idempotent, and non-destructive. The description adds meaningful behavior beyond annotations: the alias relationship with export_activities, continuation token semantics, polling cadence expectations, and duplicate-record behavior with includeRecentChanges.

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 compact and front-loaded with the core purpose. Every sentence provides actionable information: alias handling, continuation behavior, polling rules, and duplicate-record caveat. No filler or redundant restatement of the schema.

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?

With a 100%-covered input schema and an output schema present, the description covers the essential operational concerns: alias resolution, fetch avoidance, and continuation/polling behavior. The duplicate-record warning is an important completeness detail. Nothing critical is missing for an agent to use this tool 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 description coverage is 100%, so the schema already documents from and includeRecentChanges. The description adds value by explaining how the continuation token should be used in the polling loop and by clarifying that includeRecentChanges may cause repeated records, which goes beyond the schema's 'prioritize recent changes' description.

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 states a specific verb and resource: reading the incremental timesheet-activity export feed for Settings workflows. It explicitly identifies the sibling export_activities as the same feed, which clearly distinguishes the tool and prevents duplicate fetching.

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?

The description gives explicit usage guidance: use whichever name is available, do not fetch both, continue with continueFrom while hasMore is true, retain the token when false, and wait before polling again. It also warns that includeRecentChanges may repeat records, which is valuable operational guidance.

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

Deploy Server