QuickBooks Online MCP Server

delete_estimate

Remove an estimate from QuickBooks Online by specifying its ID or entity reference.

Instructions

Delete an estimate in QuickBooks Online.

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": {
      "params": "<params>"
    },
    "name": "delete_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates that the operation deletes. It says nothing about irreversibility, permission requirements, failure modes for estimates referenced by invoices or payments, or what is returned on success. For a destructive mutation this is a significant disclosure gap.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient, though in this case the terseness reflects under-specification rather than disciplined compression.

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?

With no annotations, no output schema, and a completely undocumented nested parameter, the definition leaves an agent unable to call the tool correctly without guessing. Given the surrounding family of estimate tools, the description should at minimum explain the identifier contract and deletion preconditions.

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

Parameters1/5

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

Schema description coverage is 0% and the single parameter is an untyped nested object named 'idOrEntity' with free-form additionalProperties. The description supplies no meaning at all — it never explains whether to pass a bare ID, an entity reference object, or a full estimate payload, which is the most consequential ambiguity in this definition.

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 clear verb+resource pair (delete an estimate) and names the system (QuickBooks Online), so an agent can identify the operation immediately. It does not explicitly differentiate from the many other sibling delete tools beyond the resource name, but the resource itself is unambiguous.

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 use this versus update_estimate, get_estimate, or search_estimates, and no mention of prerequisites such as whether the estimate must first be voided, closed, or detached from linked transactions. The agent must infer all routing and eligibility conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server