ServiceTitan MCP

dispatch_job_cancel_reasons_list

Read-onlyIdempotent

List job cancellation reasons using pagination, active status, and date filters to locate known reason IDs.

Instructions

Browse the paginated job-cancellation-reason catalog using active and date filters. Use dispatch_jobs_cancel_reasons_list instead only to look up a supplied set of known reason IDs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No	Return items created before this UTC timestamp
`modifiedBefore`	No	Return items modified before this UTC timestamp
`createdOnOrAfter`	No	Return items created on or after this UTC timestamp
`modifiedOnOrAfter`	No	Return items modified on or after this UTC timestamp

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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a paginated browse with active/date filters, which is useful context but largely mirrors what the schema already communicates. There is no contradictory behavioral claim.

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 two sentences with no filler. The primary purpose is front-loaded, and the sibling distinction is stated efficiently in the second sentence. Every word earns its place.

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 paginated list tool with rich schema descriptions and an output schema, the description is sufficient. It tells the agent what the tool does, how it filters, and when to choose the sibling instead. Nothing critical for tool selection or invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3 even without parameter info in the description. The description groups the parameters as 'active and date filters,' which provides a useful framing but does not add meaning beyond the schema's per-field descriptions. No parameter information is missing from 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?

The description clearly states the tool's purpose: browsing the paginated job-cancellation-reason catalog with active and date filters. It explicitly distinguishes this tool from the sibling dispatch_jobs_cancel_reasons_list, which is for looking up known reason IDs. The verb 'Browse' and the resource 'job-cancellation-reason catalog' make the scope unambiguous.

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 direction: use this tool for catalog browsing/filtering, and use dispatch_jobs_cancel_reasons_list instead only when you have a supplied set of known reason IDs. This directly routes the agent between two closely named siblings and leaves little to inference.

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

Deploy Server