Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Delete alert

delete_alert
Read-onlyIdempotent

Builds a v2 alert.delete request.

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, 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": {
      "alert_tag": "<alert_tag>",
      "owner_id": "<owner_id>"
    },
    "name": "delete_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
owner_idYes
alert_tagYes
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.

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

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

With annotations already declaring readOnlyHint=true, destructiveHint=false, and idempotentHint=true, the description's main added value is disclosing that this is a non-mutating request compiler whose output must be sent elsewhere, which is genuinely beyond what the annotations say. It also points at the response_json shape and status codes and enumerates the error codes the call can surface. It does not mention auth or permission requirements beyond implying them through error codes 3260/3261/3263.

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 purpose is front-loaded in a single clear sentence, which is good. But the bulk of the description is an 18-item error-code list that ends by admitting 'the call result explains each', making much of that enumeration redundant weight against a four-parameter request builder.

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

Completeness3/5

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

An output schema exists, so the description needn't detail return values, yet it still sketches response_json. It covers error handling well but leaves the mechanics incomplete: after receiving 'the v2 request to send', how the agent should dispatch it is never explained, and the two required identifiers remain undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the two parameters that actually lack descriptions in the schema are the required ones, alert_tag and owner_id. The description never explains what an alert_tag is, where an owner_id comes from, or the format of either, so it fails to compensate for the coverage gap on exactly the inputs an agent cannot guess.

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 states a specific verb and resource: it 'Builds a v2 alert.delete request' and returns the request plus the webhook payload the answer arrives in. This is far more precise than the title 'Delete alert' and clarifies the tool is a request builder, not an executor. It does not, however, distinguish itself from the create_alert sibling, so it stops just short of a 5.

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?

There is no guidance on when to reach for this tool versus alternatives, no prerequisites for the two required identifiers, and no statement of when not to use it. The error catalog hints at failure conditions but never explains the usage context an agent would need to select this tool.

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