QuickBooks Online MCP Server

update_sales_receipt

Update an existing QuickBooks Online sales receipt by ID, including document number, customer reference, and private note, with sync token protection.

Instructions

Update an existing sales 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_sales_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.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 behavioral burden, yet it only discloses that the record must already exist. Nothing is said about optimistic locking via sync_token, what permissions are required, whether omitted fields are preserved or cleared, or that arbitrary additional fields are accepted (additionalProperties: {}).

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 short sentence with zero padding and the key action front-loaded, which is structurally clean. However, the brevity is under-specification rather than economy: it omits information an agent needs to call the tool correctly.

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?

A mutation tool with no annotations, no output schema, a nested params object, and a required optimistic-locking token demands substantially more description than one sentence. The definition leaves the agent to infer the entire update contract from the schema alone.

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?

Reported schema coverage is 0% and the description mentions no parameter at all. The nested params object hides id, sync_token, doc_number, customer_ref, and private_note behind one top-level field, and the description does nothing to explain the id/sync_token pairing or the open-ended additionalProperties escape hatch.

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 (update) and resource (sales receipt) qualified by 'existing', so an agent knows this mutates a persisted record rather than creating one. Sibling naming (create_sales_receipt, get_sales_receipt, delete_sales_receipt, search_sales_receipts) makes the distinction obvious, but the description itself does not name or contrast any sibling.

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?

No when-to-use guidance, no prerequisites, and no mention of the read-modify-write workflow required by the sync_token that the schema mandates. It also never clarifies the create-vs-update decision, which is the most likely routing mistake an agent makes given create_sales_receipt sits right beside it.

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

Deploy Server