Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Delete data ext

delete_data_ext
Read-onlyIdempotent

This request deletes the data from the specified existing custom field or private extension. If you want to clear the data extension value (to make the custom field or private extension blank), you must use data_ext_del. The DataExtMod request can’t be used to clear the field.

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, 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": {
      "data_ext_del": "<data_ext_del>"
    },
    "name": "delete_data_ext"
  }
}

Input Schema

NameRequiredDescriptionDefault
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`.
data_ext_delYesDataExt The DataExtAdd request writes data to the specified data extension for the specified object.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description does add real value by revealing that the call returns a v2 request plus the webhook payload shape and status codes, and by enumerating failure modes (cannot_delete, in_use, locked, stale_edit_sequence). But the 16-code dump is bulk rather than insight; it says error names, not what causes or resolves them.

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 and the alternative-operation rule are correctly front-loaded, but the trailing error-code enumeration is a long undifferentiated list that dominates the text and would be better carried by the output schema. Naming the clearing operation `data_ext_del` when the required parameter is also `data_ext_del` invites confusion.

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?

With an output schema present, the description covers purpose, the sibling boundary, the return mechanism (request to send, webhook answer) and failure taxonomy—enough to invoke correctly. It leaves implicit who dispatches the returned request and what auth is needed, which is the only notable gap for a mutation-shaped operation.

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 schema already documents every nested field, including the mutually exclusive set rules. The description adds only that the target must be an *existing* custom field or private extension and does not clarify the required `data_ext_del` object beyond what the schema states. Baseline 3 applies.

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?

Opens with a specific verb and resource: 'deletes the data from the specified existing custom field or private extension.' It also draws a boundary against the `data_ext_del` operation for blanking a value. The remaining ambiguity is that the tool itself does not perform the delete—it returns a request to send—which only becomes clear in the second paragraph.

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?

Explicitly states the when-not case: to clear a value you must use `data_ext_del`, and DataExtMod can't be used for that. That is a genuine routing rule. It stops short of framing when to use this versus sibling mutations like `update_data_ext` or `delete_data_ext_def`, leaving those to inference.

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