Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_accounts_update

Sparse-update an existing QuickBooks Online account by providing its ID, SyncToken, and updated fields. Only supplied values are modified.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
NameYesAccount name (required, must be unique within parent)
ActiveNoWhether the account is active (inactive accounts are hidden)
AcctNumNoUser-defined account number (if chart-of-accounts numbering is enabled)
ParentRefNoParent account reference for sub-accounts, e.g. {"value": "42"}
SyncTokenYesCurrent SyncToken of the record (required by QBO for sparse updates; fetch the record first to obtain it)
accountIdYesThe Account ID to update
AccountTypeNoHigh-level account type, e.g. Bank, Accounts Receivable, Income, Expense, Equity, Other Current Asset (required on create)
CurrencyRefNoCurrency reference for multi-currency companies, e.g. {"value": "USD"}
DescriptionNoFree-form description
AccountSubTypeNoSpecific sub-type within the AccountType, e.g. Checking, SalesOfProductIncome
Behavior3/5

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

With no annotations, the description carries the burden. It explains the sparse-update behavior but does not disclose side effects, permissions, concurrency (SyncToken use is in schema), or error conditions. The added value is moderate beyond the schema.

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 wasted words. The first sentence front-loads the key action 'Sparse-update an existing Account record.' Every word is necessary.

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

Completeness3/5

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

Given the tool has 10 parameters and no output schema, the description explains the sparse-update concept but lacks guidance on return values, errors, or prerequisites like fetching SyncToken. Adequate but not comprehensive.

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%, so baseline is 3. The description repeats that Id and SyncToken are required, already in schema, and adds no new parameter-specific meaning.

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 'Sparse-update an existing Account record,' specifying both the verb (sparse-update) and the resource (Account record). This distinguishes it from sibling tools like qbo_accounts_create or qbo_accounts_get.

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 mentions 'Only provided fields are changed' implying partial updates, and that 'Id and SyncToken are required.' However, it does not explicitly state when to avoid this tool (e.g., for full updates or creation) nor compare to alternatives, though the context is clear.

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