Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find list deleteds

find_list_deleteds
Read-onlyIdempotent

A ListDeletedQuery will return all list elements deleted within the last 90 days, grouped according to object type.

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": {
      "list_del_type": "<list_del_type>"
    },
    "name": "find_list_deleteds"
  }
}

Input Schema

NameRequiredDescriptionDefault
meta_dataNoUse the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects).
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.
list_del_typeYesThe type of list from which a list member is being deleted.
include_ret_elementNo
deleted_date_range_filterNoFilters according to delete dates (within the last 90 days).

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
queryYesThe query parameters: the arguments you passed.
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.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description does add real context—that the call compiles a v2 request delivered via webhook, and that specific error codes (3150, 3260, etc.) can be returned—but the phrasing around 'this operation's response_json' is garbled enough that the async return path stays ambiguous, and the 90-day hard limit is stated only as a return property rather than a constraint.

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 opening sentence is well front-loaded, but the second sentence is convoluted and hard to parse ('the webhook payload QuickBooks' answer arrives in (this operation's response_json...)'), and the nine-code error dump consumes substantial space without prioritization.

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

Completeness2/5

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

An output schema exists, so return shapes needn't be explained, and the error enumeration is thorough. However, for an asynchronous webhook-delivery tool, the description never clarifies how the agent should consume the returned request and correlate the later webhook answer—the single most important behavioral detail for this operation.

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

Parameters4/5

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

Schema description coverage is 83%, so the schema already carries most parameter meaning (meta_data modes, request_id, include_qbxml, date-range bounds). The description adds only the 90-day ceiling on the deletion range, which is useful but largely redundant with the schema's own date-filter documentation; baseline 3 is met with a small lift.

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 names a specific query object and states its scope: 'return all list elements deleted within the last 90 days, grouped according to object type.' That scope (list elements vs. transactions) implicitly separates it from find_txn_deleteds, though it never names the sibling explicitly.

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 implied by the 90-day deletion window and the object-type grouping, but there is no explicit when-to-use guidance, no statement of when not to use it, and no pointer to find_txn_deleteds for transaction deletions. The agent must infer the routing rule from the sibling's name.

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