Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create inventory adjustment

create_inventory_adjustment
Read-onlyIdempotent

If the following conditions aren’t met, you will receive an error if you try to add an inventory adjustment through the SDK:

The inventory_adjustment_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, 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": {
      "account_ref": "<account_ref>",
      "inventory_adjustment_line_add": "<inventory_adjustment_line_add>"
    },
    "name": "create_inventory_adjustment"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNoAdditional information.
txn_dateNoThe date of the transaction. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
class_refNoUse classes to categorize transactions (for example, by department, location, or work type). Class tracking is off by default in QuickBooks.
def_macroNo`def_macro` lets you assign a reusable name to a returned `txn_id` or `txn_line_id` so later requests can reference it with `useMacro`. This feature requires SDK 2.0+.
ref_numberNo`ref_number` is a user-managed transaction reference (for example, a check number). It can be edited and is not guaranteed to be globally unique.
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`.
account_refYes`account_ref` points to an account in the company file. If both `full_name` and `list_id` are provided, `full_name` is ignored.
customer_refNo`customer_ref` identifies a customer or customer job. If both `full_name` and `list_id` are provided, `full_name` is ignored. In SalesReceipt and ReceivePayment, it identifies who receives credit.
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.
inventory_site_refNoSite where inventory is located.
include_ret_elementNo
inventory_adjustment_line_addYes

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
Behavior3/5

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

The annotations (readOnlyHint=true, idempotentHint=true) could look contradictory for a "create" tool, but the description reconciles this by explaining it returns the v2 request to send plus the webhook payload — i.e. a request-builder rather than a direct mutation. The error-code enumeration (code/type pairs and note that the call result explains each) adds real value beyond annotations, but the missing prerequisite list is a meaningful behavioral gap.

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 error-code list is compactly enumerated and earns its space, but the opening sentence is an incomplete fragment placed in the highest-value position, and the paragraph jumps from prerequisites to qbXML compatibility to return shape without structure. Front-loading is actively harmful here.

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?

For a 13-parameter, deeply nested creation tool, the description should at minimum spell out the preconditions it alludes to and clarify the compile-then-send workflow. It partially covers return shape and failure modes (with an output schema also present), but the dangling prerequisite sentence leaves a critical hole in an otherwise complex 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 coverage is 85% and the nested inventory_adjustment_line_add schema is thoroughly self-documented, including exclusive-choice constraints, so the baseline of 3 applies. The description contributes nothing about the required account_ref or the line-item structure, so it does not compensate for the remaining 15%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states in a complete sentence what the tool does. It opens with a dangling conditional ("If the following conditions aren't met...") whose conditions are never listed, then talks about the qbXML wrapper and return payloads; the actual verb+resource (create an inventory adjustment in QuickBooks) is only inferable from the name and the error-code list.

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?

No when-to-use guidance and no differentiation from siblings such as update_inventory_adjustment, create_transfer_inventory, or create_item_inventory. The one sentence that gestures at prerequisites is truncated, so the agent learns that conditions exist but not what they are.

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