Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Update account

update_account
Read-onlyIdempotent

Modifies an Account.

The account_mod wrapper from qbXML is also accepted. Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3000 invalid_object_id, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 3120 object_not_found, 3140 invalid_reference, 3150 missing_element, 3170 cannot_modify, 3175 in_use, 3176 locked, 3200 stale_edit_sequence, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3263 read_only_access, 3264 merchant_services_subscription_required

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "edit_sequence": "<edit_sequence>",
      "list_id": "<list_id>"
    },
    "name": "update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNoA descriptive text field.
nameNoName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
list_idYesQuickBooks' ID for the record. Used over `full_name` when both are sent.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
parent_refNoA reference to the list object that is one level above this one.
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
bank_numberNoThe bank account number or an identifying note about the account.
tax_line_idNoAn internal representation of the tax line associated with this account.
account_typeNoThe type of QuickBooks account. You can’t create or modify a non-posting account through the SDK, because QuickBooks creates these accounts behind the scenes.
currency_refNoA currency record defines how QuickBooks stores and displays a currency. Built-in currency name/code values are fixed; formatting and active status can vary by settings and workflow.
open_balanceNoThe amount of money in, or the value of, this account as of `open_balance_date`. On a bank statement, the amount of money in the account at the beginning of the statement period.
edit_sequenceYes`edit_sequence` is a server-generated revision token. It changes each time the object is updated. To modify an existing object, you must send the current `edit_sequence`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
account_numberNoAccount numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs.
open_balance_dateNoThe date when an opening balance was entered for this account.
sales_tax_code_refNo`sales_tax_code_ref` points to the sales-tax code used for an item or customer context. QuickBooks includes default TAX and NON codes, and a code can be deleted only when nothing references it.
include_ret_elementNo

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
bodyYesThe JSON body: the arguments you passed.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new context: the accepted qbXML `account_mod` wrapper, the two-part return (v2 request + webhook payload shape), and an enumerated error catalog with codes such as 3200 stale_edit_sequence and 3261 personal_data_access_denied. That error list is high-value for an agent planning recovery paths. The notable gap is update semantics — whether omitted fields are preserved or cleared — which is the single most consequential behavior for a modify operation and is never stated; the headline "Modifies an Account" also sits awkwardly against readOnlyHint=true, though the body's framing as a request compiler reconciles it.

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

Conciseness3/5

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

The lead sentence is short and front-loaded, which is good. The second sentence is a dense run-on combining three separate facts (wrapper alias, returned request, webhook payload) in one breath, and the trailing error list is a long unpunctuated dump. The error codes earn their place, but the formatting makes it harder to scan than 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?

Output schema exists, so return values needn't be explained, and the description does cover the request/webhook split and error handling well. However, for a 17-parameter mutation with nested references, the absence of partial-update semantics and of any note on which optional fields behave destructively leaves a real hole. Adequate, but not complete for the tool's complexity.

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 94%, so the schema already carries nearly all parameter meaning, and the baseline of 3 applies. The description adds only marginal semantics: the qbXML wrapper name, and indirectly the importance of edit_sequence via the 3200 stale_edit_sequence error. No parameter in the description is explained beyond what the schema states.

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

Purpose4/5

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

The first sentence names a specific verb and resource ("Modifies an Account"), which cleanly separates it from create_account and the non-account update_* siblings by name. The second sentence clarifies that the tool actually compiles and returns a v2 request plus the webhook payload, which is the more precise statement of purpose. It stops short of an explicit contrast with siblings such as create_account, but the resource and verb are unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of returning "the v2 request to send" and "the webhook payload QuickBooks' answer arrives in" sketches the workflow (call, send, await webhook) without ever saying when to prefer this over create_account or the qbXML path. There is no statement of prerequisites beyond what the schema already declares (edit_sequence, list_id required). An agent can infer the flow but gets no explicit when-to-use or when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources