Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create item other charge

create_item_other_charge
Read-onlyIdempotent

Adds an other charge item: a charge that isn't a service or a product, such as delivery, setup fees or service charges. Send sales_or_purchase for a charge the business only sells or only buys, or sales_and_purchase for one it does both with.

The item_other_charge_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": {
      "name": "<name>"
    },
    "name": "create_item_other_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
bar_codeNoBarcode reference information.
class_refNoUse classes to categorize transactions (for example, by department, location, or work type). Class tracking is off by default in QuickBooks.
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`.
external_guidNoAllows for the attachment of a user defined GUID value.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
is_tax_includedNoFor future use with international versions of QuickBooks.
sales_or_purchaseNoA `sales_or_purchase` aggregate is used for items that are meant to be either purchased or sold, but not both. Choose exactly one of: `sales_or_purchase`, or `sales_and_purchase`.
sales_and_purchaseNoA `sales_and_purchase` aggregate is used for items that are meant to be both purchased and sold, such as an “other charge” item that is reimbursable. Choose exactly one of: `sales_or_purchase`, or `sales_and_purchase`.
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.8/5.0
Behavior4/5

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

The description carries substantial behavior the annotations do not: it discloses that the tool does not apply the change directly but 'Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in,' that the qbXML `item_other_charge_add` wrapper is accepted, and it enumerates the error codes/types with the note that the result explains each. This resolves the tension between 'Adds' and readOnlyHint=true into an explicit request-builder contract, though it says nothing about permissions or rate limits beyond listing permission-related error codes.

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?

Purpose and the required sales_or_purchase fork are front-loaded, which is good structure. But roughly half the text is a 20-item error-code list that the description itself says is explained by the call result, making it bulk that the agent will rarely act on at selection time.

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 13-parameter nested-object tool with an output schema and full annotations, this is close to complete: it explains what is returned (v2 request + webhook payload), the accepted input wrapper, and the failure surface, while the output schema absorbs the return-shape burden. The only gap is that it never states the effect on the company file at call time versus after the request is sent.

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 92%, so the schema already documents nearly every parameter (barcode override, class/parent refs, include_qbxml, etc.) and the baseline applies. The description adds only the sales_or_purchase vs sales_and_purchase mutual-exclusion rule and the qbXML alias, both of which are largely repeated or implied in the schema's own 'Choose exactly one of' text — no additional syntax or format guidance.

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 first sentence gives a specific verb+resource ('Adds an other charge item') and then defines the resource by exclusion: 'a charge that isn't a service or a product, such as delivery, setup fees or service charges.' That definition directly distinguishes it from the many create_item_service / create_item_inventory / create_item_discount siblings, so an agent can pick it without opening the schema.

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 a clear rule for the internal fork ('sales_or_purchase' for a charge only sold or only bought, 'sales_and_purchase' for both), which is real when-to-use guidance at the parameter level. However it never says when to choose this over create_special_item, create_item_service, or update_item_other_charge — no create-vs-update or create-vs-sibling routing is stated, so usage is only partially covered.

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