Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create item non inventory

create_item_non_inventory
Read-onlyIdempotent

Adds a non-inventory item: something the business buys but doesn't stock, such as office supplies, or materials bought for one job and billed to the customer. Send sales_or_purchase for an item it only sells or only buys, or sales_and_purchase for one it does both with.

The item_non_inventory_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_non_inventory"
  }
}

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
unit_of_measure_set_refNoThe unit of measure set consists of a base unit and 0-n related units.
manufacturer_part_numberNoThe part number used by the manufacturer of the item.

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 goes beyond the annotations by explaining the tool's actual contract: it returns the v2 request to send and the webhook payload the answer arrives in, which explains why readOnlyHint=true is coherent despite the word 'Adds'. It also discloses the qbXML alias 'item_non_inventory_add' and enumerates the failure surface (name_in_use, not_authorized, read_only_access, locked). The error list is delegated to the call result rather than elaborated, which limits the added value somewhat.

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 opening sentence is well front-loaded and the item definition earns its place. The second paragraph mixes genuinely useful framing (returns the request and webhook payload, qbXML alias) with a 21-code error dump that the description itself says the call result will explain, which is padding relative to the tool's core contract.

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?

With an output schema present, a complete annotation set, and 93% schema coverage, the description need only supply the operational framing — and it does: what is produced, the alternative qbXML entry point, and the response channel. It is not fully complete on permissions or uniqueness/hierarchy behavior, but those are covered by schema field descriptions and error codes.

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 93% and the nested aggregates are thoroughly self-documented, so the schema carries the parameter burden and the baseline of 3 applies. The description adds only the semantic intent behind the sales_or_purchase choice, restating what the schema already states as 'Choose exactly one of'.

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?

Specific verb plus resource ('Adds a non-inventory item') with a plain-language definition of the category — bought but not stocked — so an agent can distinguish it from inventory items. The sibling create_item_service / create_item_other_charge boundaries are not named, so the differentiation is conceptual rather than explicit.

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 description gives real guidance on the sales_or_purchase vs sales_and_purchase choice ('only sells or only buys' vs 'does both'), which is the main branch point of the call. It offers no guidance on when to use this tool versus sibling creation tools for services, other charges, or inventory items, and no prerequisites or when-not conditions.

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