ServiceTitan MCP

pricebook_materials_list

Read-onlyIdempotent

List material pricebook items page by page, filtering by IDs, cost types, direct-cost status, activity, timestamps, or external data.

Instructions

List one requested page of material pricebook items using IDs, cost-type IDs, other-direct-cost state, active state, timestamps, and external-data mappings. Use pricebook_materials_get for a known item, pricebook_materials_cost_types_list for cost metadata, or inventory tools for stock movement.

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)
`costTypeIds`	No	Comma-separated cost type IDs
`includeTotal`	No	Include total count in response
`createdBefore`	No
`modifiedBefore`	No
`externalDataKey`	No	External data key filter
`createdOnOrAfter`	No
`isOtherDirectCost`	No	Filter by other direct cost materials
`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, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful context beyond those annotations by clarifying that only one requested page is returned and by summarizing the available filters (timestamps, external-data mappings, etc.). It does not discuss pagination defaults or response shape, but the output schema covers return structure.

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 filler. The first sentence front-loads the tool's core behavior and filtering scope; the second efficiently names the alternatives. Every phrase contributes to selection or invocation.

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 15-parameter, zero-required list tool with a rich output schema and read-only annotations, the description is sufficiently complete. It states the operation, scopes the result to one page, summarizes filter dimensions, and routes to key alternatives. It could mention pagination parameters by name, but the schema already documents them, so nothing critical is missing.

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 description coverage is 73%, and the schema already documents each parameter with its purpose. The description groups parameters into categories ('IDs, cost-type IDs, other-direct-cost state, active state, timestamps, and external-data mappings'), which helps orient the agent but does not add new semantic details beyond what the schema already provides. Baseline 3 is appropriate.

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 action ('List one requested page of material pricebook items') and enumerates the filtering dimensions. It also distinguishes itself from closely related tools by naming pricebook_materials_get, pricebook_materials_cost_types_list, and inventory tools, so an agent can separate it from siblings without opening schemas.

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 gives explicit routing guidance: use pricebook_materials_get for a known item, pricebook_materials_cost_types_list for cost metadata, and inventory tools for stock movement. This directly tells the agent when to choose this tool versus alternatives, leaving little to inference.

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

Deploy Server