ServiceTitan MCP

settings_business_units_list

Read-onlyIdempotent

Retrieve a paginated list of business units with filters by ID, name, active status, date ranges, or external data application. Use to locate business units for further retrieval or synchronization.

Instructions

List one requested page of business units, optionally filtered by IDs, name, active state, dates, or external-data application. 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 IDs (max 50)
`name`	No	Business unit name filter
`page`	No	Page number (starts at 1)
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`externalDataApplicationGuid`	No	External data application GUID

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. Description adds pagination and filter context without contradicting annotations. No additional side effects or rate limits mentioned, but annotations cover safety adequately.

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, no fluff. Front-loads the core action and filters, then points to alternatives. Highly concise and structured.

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 an output schema present, return format is covered. Description covers pagination, filter options, and alternative tools. Minor gap: no mention of default page size beyond the parameter description, but overall adequate for correct invocation.

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% (7 of 11 parameters described). Description mentions 'IDs, name, active state, dates, or external-data application' which adds general meaning, but does not explain the difference between before/onOrAfter date filters or other undocumented parameters. Falls short of fully compensating for missing schema descriptions.

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?

Description clearly states a list action with pagination and filter options, distinguishing it from the get tool (single known ID) and export feed (synchronization). The verb 'List' plus resource 'business units' is specific and unambiguous.

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?

Explicitly instructs when to use alternatives: 'Use the get tool for one known ID or the export feed for synchronization.' This provides clear guidance on tool selection and when not to use this list endpoint.

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

Deploy Server