QuickBooks Online MCP Server

delete_purchase_order

Delete a purchase order in QuickBooks Online by specifying its ID or entity reference to remove outdated or incorrect orders from your accounting records.

Instructions

Delete a purchase order 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_purchase_order"
  }
}

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 supplied, so the description carries the full burden and does almost nothing with it. "Delete" signals a destructive operation, but nothing is said about irreversibility, whether linked bills/transactions block deletion, required permissions, or error behavior — critical facts for a destructive QuickBooks entity operation.

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?

A single front-loaded sentence with no wasted words, which is structurally clean. However, at this length it is under-specified rather than genuinely concise, leaving no room for the operational detail a destructive tool needs.

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?

For a destructive, no-annotation, no-output-schema tool with an undefined nested parameter, the definition is too thin to support confident invocation. It should at minimum clarify the identifier format, deletion preconditions, and what is returned or lost on success.

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 description coverage is 0% and idOrEntity is declared as an empty nested object, so the agent cannot tell whether to pass a raw QuickBooks ID string or a full entity payload, nor what additional fields are accepted via additionalProperties. The description adds no meaning beyond the parameter name itself.

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 gives a specific verb and resource ("Delete a purchase order") in a stated product context (QuickBooks Online), which cleanly separates it from sibling writers like delete_purchase, delete_invoice, and delete_bill. It does not explain how a purchase order differs from a QuickBooks "Purchase" (delete_purchase exists as a sibling), so it stops short of full sibling disambiguation.

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_purchase_order, get_purchase_order, or search_purchase_orders, and no mention of preconditions such as whether the PO must be open or unlinked. The agent is left to infer the entire usage context from the verb alone.

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

Deploy Server