Skip to main content
Glama
montrellcruse

ServiceTitan MCP

by montrellcruse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

estimates_estimate_templates_list

Read-onlyIdempotent

Retrieve paginated estimate templates, filtered by active status and modified date range, to quickly locate specific templates.

Instructions

List one requested page of estimate templates, filterable by active state and modified timestamps. Use estimates_estimate_templates_get for a known template ID; use estimates_list for customer estimates created from templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starts at 1)
activeNoFilter by active statusTrue
pageSizeNoRecords per page (default 50)
includeTotalNoInclude total count in response
modifiedBeforeNoReturn templates modified before this UTC timestamp
modifiedOnOrAfterNoReturn templates modified on or after this UTC timestamp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.0.0
    • 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"
+}
  2. Addedv2.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destructive action, so the safety profile is covered. The description adds meaningful behavioral context by noting pagination, filtering by active state and modified timestamps, and the distinction from related list endpoints. No contradiction with 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, no filler. The first sentence states the core purpose and key filters; the second provides targeted routing guidance. Every clause 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?

For a paginated list endpoint with full schema descriptions, a rich output schema, and strong read-only annotations, the description is complete. It covers what the tool returns, the principal filters, pagination, and how it differs from the closest sibling tools.

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%, and each parameter already has a clear description. The tool description adds only a high-level summary of filtering by active state and modified timestamps, which is helpful orientation but does not meaningfully expand on the schema's parameter-level explanations.

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 states a specific verb ('List'), a concrete resource ('estimate templates'), and the paging/filtering scope. It also names sibling alternatives (estimates_estimate_templates_get, estimates_list), making the tool's role unambiguous within a large sibling set.

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 gives routing guidance: use estimates_estimate_templates_get for a known template ID and estimates_list for customer estimates created from templates. This tells an agent when to use this tool versus 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

Other Tools