Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_items_update

Update a QuickBooks Online Item record partially by providing only the fields to change, along with the Item ID and SyncToken.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
NameYesItem name (required, must be unique)
TypeNoItem type: Inventory, NonInventory, or Service. Required on create unless QBO infers it.
itemIdYesThe Item ID to update
TaxableNoWhether the item is taxable on sales
QtyOnHandNoInitial on-hand quantity (Inventory items only)
SyncTokenYesCurrent SyncToken of the record (required by QBO for sparse updates; fetch the record first to obtain it)
UnitPriceNoDefault sales price
DescriptionNoSales description
InvStartDateNoInventory start date (YYYY-MM-DD, Inventory items only)
PurchaseCostNoDefault purchase cost
PurchaseDescNoPurchase-side description
AssetAccountRefNoAsset account reference, required for Inventory items, e.g. {"value": "81"}
IncomeAccountRefNoIncome account reference, e.g. {"value": "79"} (required for Inventory and Service items)
ExpenseAccountRefNoExpense or COGS account reference, e.g. {"value": "80"} (required for Inventory and NonInventory items)
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It correctly explains the sparse update behavior and required fields, but does not disclose possible side effects, error conditions, or response format. Minimum viable transparency for a mutation tool.

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 just two sentences, front-loaded with the core action ('Sparse-update an existing Item record.') followed by a critical detail. No wasted words.

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?

Given the complexity of QBO sparse updates (14 parameters, 100% schema coverage, no output schema), the description adequately covers the update mechanism and essential fields. It could mention the need to fetch the item first to obtain SyncToken, but the parameter description already handles that.

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%, so baseline is 3. The description adds value by clarifying the sparse update pattern and emphasizing the critical requirement of the SyncToken, which is not obvious from the schema alone.

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 explicitly states 'Sparse-update an existing Item record', using a specific verb and resource. It distinguishes itself from sibling tools like qbo_items_create (create new items) and qbo_items_get/list (retrieve items).

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?

The description clearly indicates this tool is for updating existing items, with emphasis on sparse update semantics. It specifies required fields (Id and SyncToken) but lacks explicit when-not-to-use guidance or comparisons to alternative update methods.

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