ServiceTitan MCP

people_technician_shifts_list

Read-onlyIdempotent

List technician shifts with filters for technician, type, date range, text, and active status, covering normal, on-call, and time-off shifts.

Instructions

List one requested page of technician shifts, including normal, on-call, and time-off shifts. Filter by technician, time bounds, text, type, or active state; use the get tool for one known shift ID.

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)
`shiftType`	No	Shift type filter
`includeTotal`	No	Include total count in response
`noteContains`	No	Filter shifts by note substring
`technicianId`	No	Technician ID filter
`createdBefore`	No
`titleContains`	No	Filter shifts by title substring
`endsOnOrBefore`	No	Return shifts ending on or before this UTC timestamp
`modifiedBefore`	No
`startsOnOrAfter`	No	Return shifts starting on or after this UTC timestamp
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No

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

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, lowering the burden on the description. The description adds useful behavioral context by noting pagination ('one requested page'), the shift categories returned, and the available filter dimensions without contradicting annotations.

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?

A single, front-loaded sentence communicates purpose, scope, filter capabilities, and the alternative tool with no redundant or filler content.

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 input schema, output schema, and comprehensive annotations, the description covers the essential decisions: what is listed, how it is paginated, what filters exist, and when to switch to the get tool. No critical operational detail is missing.

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 coverage is 73%, and many parameters already have descriptions. The description adds high-level semantic grouping ('technician, time bounds, text, type, or active state') that helps the agent map parameter families to intent, especially for the four undocumented timestamp parameters which fall under 'time bounds'.

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 ('List'), a concrete resource ('one requested page of technician shifts'), and enumerates the shift types included ('normal, on-call, and time-off'). It also distinguishes this from the get tool for a single known shift ID, making its purpose unmistakable.

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 clear usage context: use this when you need a paginated, filterable list of shifts, and use the get tool when you already know a specific shift ID. This is an explicit when-to-use vs alternative statement.

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

Deploy Server