ServiceTitan MCP

people_technicians_list

Read-onlyIdempotent

Fetch technician records in pages, filtering by IDs, names, active status, or creation/modified dates. Provides targeted access to ServiceTitan technician data for reporting or synchronization.

Instructions

List one requested page of technicians, optionally filtered by IDs, user IDs, name, active state, or dates. Use the get tool for one known ID or the export feed for synchronization.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated technician IDs (maximum 50)
`name`	No	Filter technicians by name (case-insensitive contains)
`page`	No	Page number (starts at 1)
`active`	No	Filter by active status	True
`userIds`	No	Comma-separated user IDs (maximum 50)
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`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.5/5.0

Behavior4/5

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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond annotations by clarifying pagination semantics ('one requested page') and the optional filter dimensions. It does not contradict the 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?

Two concise sentences with no filler. The main behavior is front-loaded, and the alternative routing is stated in a separate, clearly purposeful sentence.

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 with 11 parameters, an output schema, and strong annotations, the description covers the essential usage context: pagination, filtering, and routing to get/export alternatives. Parameter details and return shape are adequately handled by the schema and output schema.

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 coverage is 64%, so the description does not fully delegate parameter meaning to the schema. It usefully groups the filters into categories (IDs, user IDs, name, active state, dates) and notes optionality, but it does not explain the individual date-parameter semantics or add substantial detail beyond 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 action ('List'), the resource ('technicians'), and the core behavior (one requested page with optional filters). It also distinguishes itself from the get tool and export feed, which helps an agent tell it apart from sibling tools like people_technicians_get and export_technicians.

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 second sentence gives explicit guidance on when to use alternatives: 'Use the get tool for one known ID or the export feed for synchronization.' This directly addresses when not to use this tool and names the alternative categories.

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

Deploy Server