Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create sales tax code

create_sales_tax_code
Read-onlyIdempotent

Adds a sales tax code. Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:

The sales_tax_code_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": {
      "is_taxable": "<is_taxable>",
      "name": "<name>"
    },
    "name": "create_sales_tax_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNoDesc gives a longer explanation of Name.
nameYesShort name that will appear on sales forms to identify the tax status of an item. The Desc element gives a longer explanation of Name. Name must be unique, and it isn’t case-sensitive.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
is_taxableYesIndicates whether this sales-tax code is tracking taxable sales. For any particular sales-tax code, `is_taxable` can’t be modified once the sales-tax code has been used in a transaction.
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`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
item_sales_tax_refNoAn ItemSalesTax entry represents one tax rate paid to one tax agency. Use it when a transaction needs a single tax calculation. For multi-rate scenarios, use a sales-tax group instead.
include_ret_elementNo
item_purchase_tax_refNoFor future use with international versions of QuickBooks.

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

C2.4/5.0
Behavior1/5

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

The description describes an additive write ("Adds a sales tax code") while the annotations declare readOnlyHint=true and idempotentHint=true, an outright contradiction of the tool's own name and text. Beyond that conflict, it does not disclose permissions required, whether creation is reversible, or that is_taxable becomes immutable once used — an important behavioral rule only found in 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.

Conciseness2/5

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

The text is poorly ordered and includes a dangling sentence ending in a colon ("...appear on the sales-tax code list by default:") with nothing following. A long enumerated error-code block dominates the description, and the most decision-relevant statement — that this is a create operation with a qbXML alias — is buried after unrelated default-code trivia.

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

Completeness2/5

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

An output schema exists, yet the description spends a sentence explaining the response_json shape and webhook delivery rather than covering what it alone can add: permission requirements, the immutability rule for used codes, and side effects. Given nine parameters including two nested reference objects, this leaves meaningful gaps for a mutation tool.

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 89%, so the input schema already explains name, is_taxable, item_sales_tax_ref, and the rest, which sets the baseline at 3. The description adds no parameter meaning of its own beyond repeating the tax-code concept and the qbXML wrapper alias, so it neither compensates nor detracts.

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?

"Adds a sales tax code" is a specific verb plus resource, and the follow-up sentence explains what a sales-tax code actually represents (taxable vs non-taxable and why). It does not, however, distinguish this tool from nearby siblings such as create_item_sales_tax or create_item_sales_tax_group, so an agent cannot tell from the text which create to pick.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus update_sales_tax_code, create_item_sales_tax, or the find_* siblings, nor any prerequisites such as permissions or the fact that the two default codes already exist. The only guidance offered is that a qbXML wrapper name is also accepted, which is an invocation detail rather than usage 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