ServiceTitan MCP

pricebook_services_list

Read-onlyIdempotent

Retrieve a paginated list of service pricebook items filtered by IDs, active status, creation or modification dates, and external data mappings. Use it to find services for estimates or invoices.

Instructions

List one requested page of service pricebook items using IDs, active state, created or modified timestamps, and external-data mappings. Use pricebook_services_get for one known item; use estimates or invoices for services quoted or sold on customer transactions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated IDs (max 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, Code, DisplayName, CreatedOn, ModifiedOn, Price, MemberPrice, AddOnPrice, AddOnMemberPrice, MaterialsCost, PrimaryVendor, Cost, Manufacturer, Priority
`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
`externalDataKey`	No	External data key filter
`createdOnOrAfter`	No
`modifiedOnOrAfter`	No
`externalDataValues`	No	External data values filter
`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 destructiveHint=false, so the description does not need to restate safety. It adds useful behavioral context by emphasizing pagination ('one requested page') and by enumerating the filterable data dimensions, though it does not clarify before/on-or-after semantics for the timestamp filters.

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?

The description is two tight sentences with no filler: the core operation and filter dimensions come first, followed by alternative tool routing. Every sentence earns its place.

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?

For a 13-parameter list tool, the description is lean but sufficient when combined with the schema, annotations, and output schema. It defines the resource, pagination behavior, major filters, and sibling alternatives; only a pointer to bulk export tools like export_services would make it slightly more complete.

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 description groups the 13 optional parameters into meaningful categories (IDs, active state, timestamps, external-data mappings), which helps an agent understand the tool's capabilities at a glance. However, schema description coverage is only 69%, and the four timestamp parameters lack schema descriptions while the description merely says 'created or modified timestamps' without explaining the before/on-or-after distinction; page, sort, pageSize, and includeTotal are also left implicit.

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 opens with a specific verb and object—'List one requested page of service pricebook items'—and names the main filter dimensions: IDs, active state, timestamps, and external-data mappings. It also distinguishes itself from pricebook_services_get and from estimates/invoices, making its scope 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 explicitly routes to pricebook_services_get for a single known item and to estimates or invoices for services quoted or sold on customer transactions. These are clear when-not-to-use-this-tool signals against the most relevant alternatives.

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

Deploy Server