Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create special account

create_special_account
Read-onlyIdempotent

Adds a special account of the specified type to QuickBooks. A special account is an account normally created automatically as needed within the QuickBooks UI, or in the SDK via the SpecialAccountAdd request. Notice that default names for each account type are used, so there is no provision for a name field here.

The special_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": {
      "special_account_type": "<special_account_type>"
    },
    "name": "create_special_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
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`.
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.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
include_ret_elementNo
special_account_typeYesIf `special_account_type` returns a value, then QuickBooks automatically created this account when it was needed.

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?

The description reconciles the readOnly annotation by explaining that the tool returns the v2 request to send plus the webhook payload the answer arrives in, rather than performing the write itself. It also discloses the qbXML alias accepted and enumerates the error codes to handle, adding real context beyond the annotations. It stops short of describing validation or prerequisites beyond the error list.

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 purpose and return-mechanics sentences are front-loaded and efficient, but roughly half the text is a 25-item error-code dump with no grouping or guidance on which are actionable. It is information-dense rather than wasteful, but poorly balanced.

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 creation tool with an output schema and rich annotations, the definition covers scope, return mechanics, and failure modes adequately. Only the absence of explicit sibling routing keeps it from full completeness.

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?

With 80% schema coverage the schema already documents most parameters, and the description's key addition is explaining why there is no name field (default names per account type). That is genuinely useful, but the remaining parameters (currency_ref, request_id, include_qbxml, include_ret_element) get no added meaning from the description.

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?

States a specific verb and resource ('Adds a special account of the specified type to QuickBooks') and defines what a special account is, so the agent can distinguish it from a generic account. It never names the sibling create_account, so the differentiation against that tool is left implicit.

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?

The note that a special account is 'normally created automatically as needed within the QuickBooks UI' hints that this is only for edge cases, which is useful implied guidance. However, there is no explicit when-to-use/when-not statement and no mention of create_account as the alternative for ordinary accounts.

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