ServiceTitan MCP

export_job_canceled_logs

Read-onlyIdempotent

Read incremental job canceled logs feed for bulk synchronization. Start with a date or token, continue while more records exist, then wait before polling again.

Instructions

Read the incremental job canceled logs 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?

Annotations already mark this as read-only, idempotent, open-world, and non-destructive, and the description adds substantial operational behavior beyond that: the hasMore/continueFrom polling loop, the instruction to retain the token and wait, and the caveat that includeRecentChanges can return records sooner but may repeat them. This is exactly the kind of feed-specific behavioral detail an agent needs.

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 dense but efficient, with the core purpose front-loaded and the usage protocol following in compact, imperative form. There is no fluff or repetition of schema or annotation information; every clause adds actionable guidance.

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?

Given no required parameters, an output schema already present, and minimal input schema, the description covers the essential operational lifecycle: initial call, continuation, polling behavior, and the special-case caveat for includeRecentChanges. Nothing critical for an agent to invoke and poll this feed correctly is missing.

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?

Although schema coverage is 100%, the description meaningfully extends both parameters: 'from' is explained as a start date or omitted to begin at the feed's beginning, with continuation handled via continueFrom, and includeRecentChanges is given a real tradeoff ('may return records sooner but can repeat them'). This goes well beyond the schema's simple field descriptions.

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 job canceled logs export feed for bulk synchronization.' This precisely identifies the tool as a feed-style export for canceled job logs, distinguishing it from the one-off list tool (dispatch_jobs_canceled_logs_list) and the broader set of export_* siblings by the 'incremental' and 'bulk synchronization' framing.

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 clearly establishes when this tool applies: bulk/incremental synchronization of job canceled logs. It gives concrete consumption instructions (start with a date or omit from, continue with continueFrom while hasMore is true, wait when hasMore is false). It does not explicitly name alternative tools or say when not to use it, but the bulk-feed context is clear enough for an agent to select it appropriately.

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

Deploy Server