Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Delete txn

delete_txn
Read-onlyIdempotent

Deleting a transaction removes it completely and irreversibly. (Using a TxnVoid request to void a transaction, on the other hand, sets its amount to zero but keeps a record of it in QuickBooks.)

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, 3150 missing_element, 3160 cannot_delete, 3161 closing_date_delete, 3170 cannot_modify, 3175 in_use, 3176 locked, 3200 stale_edit_sequence, 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

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_del_type": "<txn_del_type>",
      "txn_id": "<txn_id>"
    },
    "name": "delete_txn"
  }
}

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`.
txn_del_typeYesThe type of transaction to be deleted.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.

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

B3.4/5.0
Behavior1/5

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

The description explicitly describes a permanent, irreversible removal of a transaction, while annotations declare readOnlyHint=true and destructiveHint=false. A tool that 'removes completely and irreversibly' cannot be read-only or non-destructive; the structured safety profile and the prose point in opposite directions, which is exactly what an agent relies on annotations to resolve.

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 critical irreversibility/void contrast is front-loaded, which is good, but the second half is a dense unbroken run of roughly 25 error code/name pairs that crowds out the more important behavioral facts. It is organized and relevant, yet disproportionate and hard 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?

It covers the return channel (v2 request, webhook payload, response_json), the status-code handling, and the full error surface, which is more than an output schema alone would convey. What is missing is the thing that matters most for a destructive operation: no mention of required scopes, permission prerequisites, or confirmation expectations.

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% and the enum for txn_del_type is fully spelled out in the schema, so the parameters are already well documented. The description adds no additional meaning about txn_id, request_id, or include_qbxml, so the baseline of 3 applies.

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 first sentence states the specific verb and resource and its full effect ('Deleting a transaction removes it completely and irreversibly'), and immediately contrasts it with the void path, so an agent can distinguish this from execute_txn_void without opening a schema.

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?

The parenthetical explains the alternative behavior (TxnVoid zeroes the amount but keeps a record), which effectively tells the caller when deletion is the right choice. It stops short of an explicit 'use this when X, not Y' directive or naming the sibling tool execute_txn_void directly.

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