Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Execute txn void

execute_txn_void
Read-onlyIdempotent

Voids a transaction: QuickBooks keeps it, with its amounts and its lines' quantities at zero and "VOID: " in front of its memo, while deleting one removes it completely. A voided invoice keeps its number and reads back as paid. An invoice that payments paid can be voided too: each payment stays, and what it had applied to the invoice becomes its unused payment, to apply elsewhere or refund (observed on QuickBooks Enterprise 24.0, 2026-10-10).

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, 3150 missing_element, 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, 3264 merchant_services_subscription_required

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": {
      "txn_id": "<txn_id>",
      "txn_void_type": "<txn_void_type>"
    },
    "name": "execute_txn_void"
  }
}

Input Schema

NameRequiredDescriptionDefault
txn_idYes`txn_id` is the unique QuickBooks identifier for a transaction. Use it to reference that transaction in later requests.
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`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
txn_void_typeYesThe type of transaction being voided.

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.5/5.0
Behavior1/5

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

The description describes a mutating operation that changes transaction amounts and memo, but annotations declare readOnlyHint=true. The rich behavioral details are useful, but this direct contradiction is the dominant issue.

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 description is front-loaded with the core void-vs-delete behavior and then covers return payload and errors. It is dense but mostly purposeful, though the full error-code list is long.

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?

It explains the observable effect of voiding, the returned v2 request and webhook payload, and possible errors, while an output schema exists. The main incompleteness is that the stated behavior conflicts with the supplied safety annotations.

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 100%, so the input schema already documents txn_id, request_id, include_qbxml, and the txn_void_type enum. The description adds no parameter-level meaning beyond what the schema provides.

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 description states a specific verb and resource: it voids a transaction. It also distinguishes voiding from deleting by explaining that QuickBooks keeps the transaction with zeroed amounts and a "VOID: " memo prefix.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames when to choose voiding over deletion through the tradeoff of retaining versus removing the transaction. It does not explicitly name the sibling delete_txn or describe broader routing among other transaction operations.

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