Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_estimates_update

Update a QuickBooks Online estimate by changing only the specified fields. Requires estimate ID and current SyncToken to preserve other data.

Instructions

Sparse-update an existing Estimate record. Only provided fields are changed; Id and SyncToken are required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
LineYesQuote lines: {Amount, DetailType: "SalesItemLineDetail", SalesItemLineDetail: {ItemRef, Qty, UnitPrice}}.
TxnDateNoEstimate date (YYYY-MM-DD)
BillEmailNoEmail address, e.g. {"Address": "customer@example.com"}
DocNumberNoEstimate number
SyncTokenYesCurrent SyncToken of the record (required by QBO for sparse updates; fetch the record first to obtain it)
TxnStatusNoStatus: "Pending", "Accepted", "Rejected", or "Closed"
AcceptedByNoName of the customer contact who accepted
estimateIdYesThe Estimate ID to update
CustomerRefYesCustomer being quoted, e.g. {"value": "123"}
PrivateNoteNoPrivate internal note
AcceptedDateNoAcceptance date
CustomerMemoNoMemo visible to customer, e.g. {"value": "Thank you"}
ExpirationDateNoExpiration date
Behavior3/5

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

No annotations, so description carries burden. States update behavior but does not disclose error cases, permissions, or side effects beyond sparse-update.

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?

Single sentence with no fluff, directly addressing the core functionality.

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

Completeness4/5

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

With 13 parameters and nested objects, the description provides a high-level overview but misses return value or error behavior.

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

Parameters4/5

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

Schema coverage is 100%, but the description clarifies sparse-update semantics and the necessity of SyncToken, adding value beyond the schema.

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 it does a 'sparse-update' on an existing 'Estimate record', distinguishing it from create/get/list siblings.

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

Usage Guidelines4/5

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

Explains sparse-update behavior and that Id and SyncToken are required, but lacks explicit when to use vs create or how to obtain SyncToken.

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/wyre-technology/qbo-mcp'

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