ServiceTitan MCP

people_employees_list

Read-onlyIdempotent

List employees by page with filters for IDs, user IDs, name, active status, and creation/modified dates to find specific staff records.

Instructions

List one requested page of employees, 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 employee IDs (max 50)
`name`	No	Filter employees 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 (max 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.2/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful pagination context ('one requested page') and summarizes available filters, but it does not disclose defaults, limits, or date semantics. No contradiction with annotations exists.

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 sentences with no wasted words. The core action and filters are front-loaded, and the sibling routing is stated second. It earns its keep without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 optional parameters and an output schema, the description gives enough orientation for an agent to use the tool correctly. Pagination behavior and alternatives are mentioned, though date-filter semantics and default page size are left implicit and rely on the 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 only 64%, so the description partially compensates by naming filter categories that map to parameters: IDs, user IDs, name, active state, and dates. However, it does not add meaningful semantics beyond the schema's own parameter names and descriptions, especially for the undocumented date fields.

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 clear resource ('employees'), and a precise scope ('one requested page'). It enumerates the filter dimensions and explicitly contrasts with the get and export sibling tools, making its purpose immediately distinguishable.

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 explicitly says to use the get tool for one known ID and the export feed for synchronization, providing direct routing guidance. This tells an agent when to prefer the list 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