QuickBooks Online MCP Server

delete_credit_memo

Deletes a credit memo in QuickBooks Online by ID or entity reference, helping remove outdated or incorrect credit records.

Instructions

Delete a credit memo 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_credit_memo"
  }
}

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 burden for a destructive, irreversible-looking mutation. It says nothing about whether the delete is soft or permanent, whether it fails when the memo is applied or linked to an invoice/payment, or what permissions are required.

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 short sentence with no filler, and the operation is front-loaded. It is efficiently written, though the brevity contributes to the gaps in behavior and parameter detail.

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 mutation with no annotations, no output schema, and a nested, undocumented parameter object, the description is far too thin. An agent could not determine safe invocation conditions or the expected response without guessing.

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 whose property (idOrEntity) has no type, format, or description. The description adds no clarification of whether this accepts a plain Id string, an entity object, or a full memo payload, leaving the only input fully ambiguous.

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 plus resource ("Delete a credit memo") and names the system (QuickBooks Online), so an agent immediately understands the operation. It does not explicitly contrast with siblings such as get_credit_memo or update_credit_memo, but the delete prefix makes the distinction obvious.

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_credit_memo, search_credit_memos, or delete_vendor_credit. Nothing is said about prerequisites (e.g., needing the memo's Id or entity first) or about when deletion is inappropriate.

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

Deploy Server