Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create item inventory assembly

create_item_inventory_assembly
Read-onlyIdempotent

Adds an inventory assembly item, which is an item that is assembled or manufactured from other inventory items. The items and/or assemblies that make up the assembly are called components. For Premier, an assembly can have a maximum of 100 components. For Enterprise, the maximum is 500 components.

The item_inventory_assembly_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_inventory_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoMaximum number of items in inventory.
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`.
sales_descNoAppears in the Description column of a sales form when the QuickBooks user sells this item. For a fixed asset, describes the sale of the asset (for accounting purposes).
build_pointNoThe build notification point. The QuickBooks user will receive a notification when `quantity_on_hand` plus `quantity_on_order` falls below `build_point`.
sales_priceNoPrice charged for this item.
total_valueNoThe total value of this inventory. If `total_value` is included, `quantity_on_hand` must also be included and must be greater than zero.
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.
purchase_costNoAmount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item.
purchase_descNoDescription that appears in the Description column of checks, bills, credit card charges, and item receipts (when an item is reordered).
inventory_dateNoThe date when an item was converted into an inventory item from some other type of item.
is_tax_includedNoFor future use with international versions of QuickBooks.
pref_vendor_refNoThe preferred vendor for this item. If a `pref_vendor_ref` aggregate includes both `full_name` and `list_id`, `full_name` will be ignored.
cogs_account_refNoRefers to the account that QuickBooks uses to track the original cost of goods that are eventually sold. (The AccountType of this account will be CostOfGoodsSold.)
quantity_on_handNoThe number of these items in inventory. `quantity_on_hand` times `average_cost` is `total_value` in an inventory item list.
asset_account_refNoRefers to the account QuickBooks uses to track the current value of the company’s inventory. (The AccountType of this account will be FixedAsset, OtherAsset, or OtherCurrentAsset.)
income_account_refNoRefers to an income account. If an `income_account_ref` aggregate includes both `full_name` and `list_id`, `full_name` will be ignored.
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
purchase_tax_code_refNoAccount used for taxes on purchases in CA or UK.
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.
item_inventory_assembly_lineNo

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 headline "Adds" sits in tension with readOnlyHint=true, but the description explicitly resolves it by stating that the call returns the v2 request to send and the webhook payload in which QuickBooks' answer arrives — i.e. the call compiles and returns rather than writing directly. It also adds real behavior beyond annotations: Premier caps assemblies at 100 components vs Enterprise's 500, the qbXML alias `item_inventory_assembly_add` is accepted, and an enumerated error contract with codes/types is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The definition is front-loaded: concept first, then the component limit, then the return/async contract, then errors. The 20-code error dump is long and partly redundant with the parenthetical note that "the call result explains each," but it is placed last and does not obscure the core instruction.

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

Completeness5/5

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

For a 28-parameter creation tool with an output schema and full annotations, the description covers the missing pieces: what the tool returns (v2 request plus webhook payload and response_json shape), the async answer path, the component ceiling, the qbXML alias, and error handling. An agent has enough to call it correctly and interpret the result.

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% across 28 parameters, so the schema already carries the parameter semantics and a 3 is the baseline. The description adds only marginal meaning, notably the 100/500 component ceiling that constrains the item_inventory_assembly_line array; it says nothing about the account refs (asset/COGS/income) that are practically mandatory for a valid assembly.

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 gives a specific verb and resource ("Adds an inventory assembly item") and then defines the domain concept (an item assembled/manufactured from other inventory items, with components), which implicitly separates it from plain create_item_inventory. It never names a sibling such as create_build_assembly or create_item_inventory explicitly, so an agent must infer the boundary.

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?

Usage is only implied by the definition: create this when the item is manufactured from components. There is no explicit when-to-use, when-not-to-use, prerequisite (e.g. required asset/COGS/income accounts), or named alternative among the many create_* item siblings.

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