QuickBooks Online MCP Server

update_refund_receipt

Updates an existing QuickBooks Online refund receipt with revised details, using the sync token to prevent conflicting edits.

Instructions

Update an existing refund receipt 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": "update_refund_receipt"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.4/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. It reveals only that this updates an existing QuickBooks Online record, without describing required permissions, optimistic-locking behavior, side effects, reversibility, error conditions, or return behavior.

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?

The description is a single front-loaded sentence with no filler, which is concise. However, it is too terse for a mutation tool with a nested parameter object, leaving the structure underdeveloped rather than appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and a nested params object requiring id and sync_token, this description is not complete enough. It omits the key operational details an agent needs to invoke update_refund_receipt correctly.

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?

The description never mentions the required id or sync_token, nor the optional doc_number, customer_ref, or private_note fields. The params object is nested and complex, and the prose adds no meaning beyond, or even about, the schema.

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 specific verb and resource: "Update an existing refund receipt in QuickBooks Online." It is clearly a mutation on an existing refund receipt, but it does not distinguish this sibling from get_refund_receipt, create_refund_receipt, delete_refund_receipt, or update_sales_receipt.

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?

It implies the tool is for existing refund receipts but gives no explicit when-to-use guidance, prerequisites, or exclusions. It does not explain when to choose this over get_refund_receipt, search_refund_receipts, or delete_refund_receipt.

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

Deploy Server