QuickBooks Online MCP Server

delete_bill_payment

Deletes or makes a bill payment inactive in QuickBooks Online to remove incorrect or unwanted payment records from your books.

Instructions

Delete (make inactive) a bill payment 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_bill_payment"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.7/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 the important non-obvious trait that deletion is actually deactivation (the record is made inactive rather than purged), which is real value. However, it says nothing about reversibility, required permissions, effects on linked bills or reports, or what is returned.

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 zero filler; the parenthetical clarifying soft-delete is well placed. It is efficient but so terse that it leaves obvious gaps, which are scored under completeness rather than structure.

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?

This is a mutation tool with no annotations, no output schema, and a nested, entirely undocumented parameter object. The one useful disclosure (soft delete) is not enough for an agent to call it safely or know what state changes result.

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 'idOrEntity' has an empty schema with no type or format, so the description must compensate and does not. An agent cannot tell whether to pass a bare ID string or a nested entity object, nor whether 'params' wraps additional fields via additionalProperties.

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?

States a specific verb (delete) and resource (bill payment) in QuickBooks Online, and usefully clarifies that deletion is a soft 'make inactive' operation. It does not distinguish itself from nearby siblings such as delete_payment or delete-bill, so the agent must infer scope from the name alone.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. the payment must exist or be unapplied), and no routing to alternatives like update_bill_payment or delete_payment. The agent can only infer usage from the tool name.

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

Deploy Server