Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

estimates_update

Update ServiceTitan job estimates by modifying details like line items, status, pricing, and customer information to reflect changes in project scope or costs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdNoJob ID associated with the estimate
projectIdNoProject ID associated with the estimate
locationIdNoLocation ID associated with the estimate
customerIdNoCustomer ID associated with the estimate
nameNoHuman-readable estimate name
jobNumberNoJob number for estimate matching
statusValueNoEstimate status numeric value
summaryNoShort summary of the estimate
soldOnNoDate/time when the estimate was sold
soldByNoUser ID who sold the estimate
activeNoWhether the estimate is active
itemsNoEstimate line items to include
externalLinksNoExternal links attached to the estimate
subtotalNoSubtotal amount before taxes
taxNoTax amount for the estimate
businessUnitIdNoBusiness unit ID that owns the estimate
idYesEstimate ID
_confirmedNoSet to true to confirm this write operation
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/montrellcruse/servicetitan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server