Skip to main content
Glama
montrellcruse

ServiceTitan MCP Server (Enterprise)

estimates_items_update

Update or add line items to an estimate with SKU, quantity, pricing, and categorization options. Supports item groups, budget codes, and membership settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoLegacy estimate ID alias. Prefer estimateId.
qtyNoLegacy alias for quantity. Prefer quantity.
skuIdNoPricebook SKU ID for the estimate item
itemIdNoExisting estimate item ID to update; omit to add a new line item
isAddOnNoWhether this item is an add-on
skuNameNoPricebook SKU display name
quantityNoQuantity for this estimate item
unitCostNoUnit cost for this estimate item
unitRateNoLegacy alias for unitPrice. Prefer unitPrice.
unitPriceNoUnit sale price for this estimate item
_confirmedNoSet to true to confirm this write operation
chargeableNoWhether this estimate item is chargeable
estimateIdNoEstimate ID
descriptionNoDescription of the estimate item
budgetCodeIdNoBudget code ID for this item
parentItemIdNoParent estimate item ID
itemGroupNameNoItem group display name
itemGroupRootIdNoItem group root ID for categorization
useDefaultProjectLabelsNoUse default project labels for this item
membershipDurationBillingIdNoMembership duration/billing option ID
skipUpdatingMembershipPricesNoSkip updating membership prices from this item
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