ServiceTitan MCP

estimates_list

Read-onlyIdempotent

Search estimates by job, project, location, status, dates, salesperson, or total amount, returning one page of results.

Instructions

Search one requested page of estimates by job, project, location, status, dates, salesperson, or total amount. Use estimates_get for one known estimate; use estimates_export_estimates for incremental synchronization.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Comma-separated estimate IDs (maximum 50)
`page`	No	Page number (starts at 1)
`sort`	No	Sort: Field (default), +Field (asc), or -Field (desc). Fields: Id, CreatedOn, ModifiedOn, SoldOn, Total
`jobId`	No	Filter by job ID
`active`	No	Filter by active status	True
`status`	No	Filter by estimate status
`orderBy`	No	Legacy order by field accepted by ServiceTitan API
`pageSize`	No	Records per page (default 50)
`soldById`	No	Filter by seller user ID
`jobNumber`	No	Filter by job number
`projectId`	No	Filter by project ID
`soldAfter`	No	Return estimates sold on or after this date/time (UTC)
`totalLess`	No	Filter estimates with totals less than this amount
`locationId`	No	Filter by location ID
`soldBefore`	No	Return estimates sold before this date/time (UTC)
`includeTotal`	No	Include total count in response
`totalGreater`	No	Filter estimates with totals greater than this amount
`createdBefore`	No
`modifiedBefore`	No
`createdOnOrAfter`	No
`orderByDirection`	No	Legacy order direction accepted by ServiceTitan API
`soldByEmployeeId`	No	Filter by seller employee ID
`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.5/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 the important behavioral nuance that this tool returns only 'one requested page' rather than streaming all records, and it clarifies the filtering scope. This is valuable context beyond the 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 tightly written sentences: the first states the core action and scope, the second gives routing guidance. No filler, no repetition of schema details, and the most important behavioral trait (single-page search) is front-loaded.

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

Completeness5/5

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

Given the rich input schema (23 parameters, 83% covered), the presence of an output schema, and annotations covering safety and idempotency, the description supplies exactly the missing context: pagination semantics, filter scope, and sibling-tool routing. Nothing critical for correct selection or invocation is absent.

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 83%, so the parameters are already well documented. The description summarizes the filter categories conceptually and maps 'salesperson' to the seller-related parameters, providing modest added meaning, but it does not go beyond what the schema descriptions already convey.

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 resource: 'Search one requested page of estimates,' and enumerates the main filter dimensions (job, project, location, status, dates, salesperson, total). It also names the sibling tools estimates_get and estimates_export_estimates, making the tool's scope 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?

The description explicitly states when to use alternatives: 'Use estimates_get for one known estimate; use estimates_export_estimates for incremental synchronization.' This gives the agent clear selection criteria and eliminates ambiguity among closely related estimate tools.

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

Deploy Server