ServiceTitan MCP

estimates_proposal_templates_list

Read-onlyIdempotent

List proposal templates page by page, filtering by active status, modification date, or proposal type ID. Retrieve records to review or manage estimate templates.

Instructions

List one requested page of proposal templates, filterable by active state, modified timestamps, and proposal type ID. Use estimates_proposal_templates_get for a known template and estimates_proposal_types_list to resolve the type filter.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`modifiedBefore`	No	Return templates modified before this UTC timestamp
`proposalTypeId`	No	Filter by proposal type ID
`modifiedOnOrAfter`	No	Return templates modified on or after this UTC timestamp

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv3.0.0Sep 6, 2026

removedInput schema / properties / createdBefore

Removed value: -{
-  "format": "date-time",
-  "type": "string"
-}

removedInput schema / properties / createdOnOrAfter

Removed value: -{
-  "format": "date-time",
-  "type": "string"
-}

addedInput schema / properties / modifiedBefore / description

Added value: +"Return templates modified before this UTC timestamp"

addedInput schema / properties / modifiedOnOrAfter / description

Added value: +"Return templates modified on or after this UTC timestamp"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

Addedv2.6.0Jun 17, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds pagination context and filterable dimensions, but does not disclose response-level behavior such as result ordering, default active filtering behavior, or whether the output is exhaustive. This is adequate but not rich.

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 sentences with no filler. It front-loads the primary action and resource, then provides targeted alternative-tool guidance. Every sentence earns its place.

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 full parameter schema, an output schema, and strong safety annotations, the description covers the essential decision points: what is listed, how it can be filtered, and when to use sibling tools. Nothing critical is missing for an agent to invoke this tool correctly.

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 100%, so the schema already documents every parameter. The description adds a helpful summary of filterability, but it does not provide additional meaning beyond the schema. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 clearly identifies the operation as listing proposal templates, specifies pagination ('one requested page'), and enumerates the main filters. It also distinguishes itself from sibling tools by naming estimates_proposal_templates_get for retrieving a single known template and estimates_proposal_types_list for resolving type filters.

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 guides when to use this tool versus alternatives: use estimates_proposal_templates_get when a specific template is known, and estimates_proposal_types_list to resolve the proposal type filter. This gives an agent clear routing information without needing to inspect sibling schemas.

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

Deploy Server