Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create account

create_account
Read-onlyIdempotent

This message allows you to perform the same activities as a user does in the QB New Account form, which can be accessed in QB by selecting Lists->Chart of Accounts->Accounts->New. If you want the account to be a subaccount to an existing account, similar to using the SubAccount checkbox and selection list drop down in the New Account form, you use the parent_ref aggregate. Notice that the parent_ref can take either the parent account’s list_id or full_name.

The account_add 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, 3175 in_use, 3176 locked, 3180 cannot_save, 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, 3270 missing_posting_account

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": {
      "account_type": "<account_type>",
      "name": "<name>"
    },
    "name": "create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNoA descriptive text field.
nameYesName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
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_typeYesThe 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.
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.
detail_account_typeNo
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description adds real context beyond them: the call returns a v2 request to send plus the webhook payload shape (`response_json`), echoes `request_id` as qbXML `requestID`, and enumerates the error codes to handle. The statement 'this message allows you to perform the same activities as a user does in the New Account form' sits in mild tension with readOnlyHint=true, but the explicit 'Returns the v2 request to send' clarifies that the tool composes rather than executes the write, so it is consistent on balance.

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 high-value facts (request-building behavior, subaccount handling) are front-loaded, but the opening sentence wastes space on QuickBooks menu navigation, and the block of 20+ error codes dominates roughly half the text without grouping or prioritization. Trimming the UI path and summarizing error categories would sharpen it considerably.

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?

For a 16-parameter creation tool with an output schema and full annotations, the description covers the essentials: return shape, webhook flow, request_id echoing, subaccount handling, and error codes. What it lacks is guidance on which fields are conditionally required by account_type (e.g. bank_number for bank accounts, open_balance vs open_balance_date) and confirmation of whether any write occurs server-side.

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 88%, so the schema already explains nearly every field (name uniqueness, is_active default, parent_ref list_id vs full_name precedence). The description adds only the subaccount/`parent_ref` usage pattern and restates the non-posting account restriction, which is marginal added meaning over the schema.

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 description conveys that this builds a QuickBooks account-creation request equivalent to the New Account form, and it explicitly covers the subaccount case via `parent_ref`. The verb+resource is clear, but it is framed through UI navigation rather than a direct 'creates an account' statement, and it never distinguishes itself from siblings such as create_special_account or update_account.

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?

It gives useful conditional guidance for one scenario: use `parent_ref` when the account should be a subaccount, and it notes that non-posting accounts cannot be created through the SDK. It offers no when-to-use/when-not guidance against alternative tools (create_special_account, update_account) and no prerequisites or permission requirements, so usage is only partially implied.

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