QuickBooks Online MCP Server

delete_customer

Deactivates a QuickBooks Online customer to remove them from active lists and clean up outdated or duplicate records.

Instructions

Delete (make inactive) a customer 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_customer"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one important trait — the operation deactivates rather than purges the record — but says nothing about required permissions, effects on related invoices/payments, reversibility, or error behavior for missing/invalid IDs.

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 compact sentence with the resource and the key behavior front-loaded, no filler or repetition. It is arguably too terse for the ambiguity it leaves behind, but every word earns its place.

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?

For a low-complexity, single-parameter mutation with no output schema, the description covers the essential 'what' and the soft-delete nuance. It is not complete enough regarding the ambiguous idOrEntity shape and the consequences for related records, both of which an agent would need before calling it safely.

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 the single required parameter is an untyped nested object whose only field, 'idOrEntity', accepts anything and permits additionalProperties. The description says nothing about whether the caller should pass an ID string, a full entity object, or which fields matter, so it fails to compensate for the schema gap.

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 pairs the specific verb 'Delete' with the resource 'customer' and scopes it to QuickBooks Online, so it is clearly distinguishable from the many sibling delete_* tools. The parenthetical '(make inactive)' adds real meaning by clarifying this is a soft delete rather than a hard removal.

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_customer (which could presumably also deactivate a customer) or search_customers/get_customer for verification. No prerequisites, no warning about customers with open transactions or linked invoices, and no statement that the action is reversible by reactivation.

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

Deploy Server