ServiceTitan MCP

scheduling_zones_list

Read-onlyIdempotent

Retrieve a paginated list of scheduling zones, filtered by active state and created or modified timestamps, to identify geographic service areas for dispatch and scheduling.

Instructions

List one requested page of scheduling zones using active state and created or modified timestamp filters. Use scheduling_zones_get for one known zone ID; use scheduling_business_hours_list for configured operating hours rather than geographic zone definitions.

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, CreatedOn, ModifiedOn
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No	Return zones created before this UTC timestamp
`modifiedBefore`	No	Return zones modified before this UTC timestamp
`createdOnOrAfter`	No	Return zones created on or after this UTC timestamp
`modifiedOnOrAfter`	No	Return zones 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?

The description discloses that the tool returns only one requested page at a time and supports filtering by active state and created/modified timestamps. Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description adds meaningful operational context beyond those hints without contradicting them.

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?

Two tight sentences with no filler. The main action and scope are front-loaded, and the alternative-tool guidance is delivered in a compact follow-up sentence. Every clause contributes useful information.

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 paginated read-only list tool with fully documented parameters, rich annotations, and an output schema, the description provides all necessary orientation: what it lists, its paging behavior, its filter dimensions, and how it differs from relevant siblings. No critical selection or invocation information 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?

The input schema has 100% description coverage, so all nine parameters are already documented with types, defaults, and meanings. The description adds a high-level summary of filter categories but does not introduce meaning beyond the schema, which matches the baseline expectation for high schema coverage.

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 uses the specific verb 'List' with a concrete resource ('scheduling zones'), and explicitly scopes the operation to a single requested page with active-state and timestamp filters. It also distinguishes itself from scheduling_zones_get and scheduling_business_hours_list, making the tool's purpose unambiguous relative to its siblings.

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 scheduling_zones_get when a single known zone ID is needed, and use scheduling_business_hours_list when the user means operating hours rather than geographic zones. This tells the agent both when to use this tool and when to choose an alternative.

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

Deploy Server