ServiceTitan MCP

dispatch_appointments_list

Read-onlyIdempotent

Search appointments by IDs, job, project, customer, technician, status, or time ranges to locate records and retrieve paginated results.

Instructions

Search appointments by IDs, job, project, customer, technician, status, start range, or created and modified ranges. Returns one page; use dispatch_appointments_get for a known ID.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated appointment IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, ModifiedOn, CreatedOn
`jobId`	No	Filter by job ID
`number`	No	Filter by appointment number
`status`	No	Filter by appointment status
`unused`	No	Return unused appointments only
`pageSize`	No	Records per page (default 50)
`projectId`	No	Filter by project ID
`customerId`	No	Filter by customer ID
`includeTotal`	No	Include total count in response
`startsBefore`	No	Return appointments starting before this UTC timestamp
`technicianId`	No	Filter by assigned technician ID
`createdBefore`	No	Return appointments created before this UTC timestamp
`modifiedBefore`	No	Return appointments modified before this UTC timestamp
`startsOnOrAfter`	No	Return appointments starting on or after this UTC timestamp
`createdOnOrAfter`	No	Return appointments created on or after this UTC timestamp
`modifiedOnOrAfter`	No	Return appointments 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.5/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds value by disclosing that results are paginated ('Returns one page'), which is a genuine behavioral trait beyond the annotations. It does not introduce contradictions or hidden side effects.

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 a single, front-loaded sentence that names the tool's purpose, enumerates its major filters, and gives routing advice. Every element earns its place, with no wasted words or redundant restating of the name.

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 the rich 18-parameter schema, the output schema, and annotations covering safety and idempotency, the description is complete for a list tool. It covers pagination, known-ID routing, and the core search dimensions, leaving no significant gap for an agent to call it correctly.

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 parameters are already fully documented. The description provides a useful high-level summary of filters, but it does not add semantics beyond what the schema already states. Baseline 3 is appropriate.

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 action ('Search appointments') and a clear resource, listing the main filter dimensions (IDs, job, project, customer, technician, status, dates). It differentiates itself from the sibling dispatch_appointments_get by explicitly directing known-ID lookups to that tool.

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 clear usage context: this is a search/list tool that returns one page. It explicitly names an alternative for a known ID (dispatch_appointments_get), helping an agent decide between the two related appointment tools. This is sufficient guidance for the search-vs-single-get decision.

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

Deploy Server