ServiceTitan MCP

estimates_items_list

Read-onlyIdempotent

Search pageable estimate line items by estimate ID, item IDs, active state, or creation and modification dates. Returns individual items attached to an estimate, not estimate headers.

Instructions

Search one requested page of estimate line items by estimate ID, item IDs, active state, or creation and modification dates. Each result represents an item attached to an estimate, rather than an estimate header returned by estimates_list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated estimate item IDs (maximum 50)
`page`	No	Page number (starts at 1)
`active`	No	Filter by active status	True
`pageSize`	No	Records per page (default 50)
`estimateId`	No	Filter by estimate ID
`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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: pagination behavior ('one requested page') and the item-vs-header distinction, which go beyond 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 sentences, front-loaded with the core action and resource, then a concise clarifying contrast with estimates_list. Every sentence earns its place with no filler or 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?

For a read-only paginated list tool with an output schema and robust annotations, the description contains the essential meaning: what is returned, how pages work, and how it differs from the sibling estimates_list. It is complete enough for an agent to select and call the tool correctly, though it does not mention bulk export alternatives.

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 summarizes the filter dimensions: estimate ID, item IDs, active state, and creation/modification dates, which partially maps to the schema. Schema descriptions cover 6/10 parameters; the four date parameters lack schema descriptions and the description only groups them without explaining the precise before vs on-or-after semantics. Parameter names are fairly self-descriptive, so this is adequate but not thorough.

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?

States a specific verb and resource: 'Search one requested page of estimate line items'. Clearly distinguishes from estimates_list by explaining this returns line items, not estimate headers. No ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names estimates_list as the closest alternative and clarifies the difference: this returns items attached to an estimate, while estimates_list returns headers. It gives useful selection context, though it doesn't mention export alternatives or explicit when-not-to-use conditions.

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

Deploy Server