Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create item subtotal

create_item_subtotal
Read-onlyIdempotent

Adds a subtotal item. On a sales form, a subtotal item will add up the amounts of the item lines above it, up to the previous subtotal.

The item_subtotal_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, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 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_subtotal"
  }
}

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.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
item_descNoThe description that will appear on a sales form when the item is used.
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.
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.7/5.0
Behavior4/5

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

This is the description's strongest section: it resolves the apparent write-vs-readOnlyHint tension by explaining that the call returns the v2 request to send plus the webhook payload in which QuickBooks' answer arrives, i.e. the tool compiles rather than executes. It also discloses the accepted qbXML wrapper alias (`item_subtotal_add`) and enumerates the error codes that can come back, which is genuine behavior beyond the annotations. The only gap is that it does not state whether reusing a name is what triggers 3100/3175 or how duplicate submissions behave despite idempotentHint=true.

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?

Well front-loaded: purpose and sales-form semantics first, then the qbXML alias, then return shape, then errors. The ~20-code error enumeration is bulk that the text itself says 'the call result explains each', so it is the one part that does not fully earn its space, but the structure remains easy to scan.

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 create tool with 8 parameters (nested object), an output schema, and an asynchronous webhook round-trip, the description covers what the agent needs to invoke it correctly and what to do with the response. Return-shape detail is partly redundant with the output schema, and name-uniqueness/hierarchy prerequisites live only in the schema, but nothing critical is absent.

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 88%, so the schema already documents all eight parameters, including the nested bar_code object and the include_qbxml/include_ret_element debug switches. The description adds no per-parameter meaning; the only implicit link is that `include_qbxml` relates to the mentioned qbXML compilation, which the schema already states. Baseline 3 is appropriate.

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 opening verb+resource ('Adds a subtotal item') is specific, and the following sentence explains the domain semantics of a subtotal (sums item lines above it, up to the previous subtotal). The distinction from the sibling update_item_subtotal is implied by 'Adds' rather than stated, but an agent can still pick it confidently.

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: 'Adds ... On a sales form' tells the agent this is the create path for a subtotal line, but there is no explicit when-to-use/when-not guidance, no prerequisite (e.g. permissions or required parent/hierarchy scope for the name), and no routing to update_item_subtotal for modifying an existing subtotal.

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