QuickBooks Online MCP Server

update_payment

Update an existing QuickBooks Online payment by ID and sync token to change its amount, customer, payment method, or private note.

Instructions

Update an existing 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": "update_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.9/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 and delivers almost none of it. It does not say that this is a mutation, whether it is a partial patch or a full replacement, that the sync_token enforces optimistic locking (and what happens on a stale token), or what permissions are needed.

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 padding or redundancy. It is efficient, though its brevity is achieved by omission rather than by tight compression of useful content.

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 a nested object parameter, no annotations, and no output schema, which is precisely the case where the description must do heavy lifting. One sentence restating the name and resource is not enough to call this safely or correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported as 0% at the top level, and the description adds no field-level meaning. Mitigating this, the nested object schema does document all six sub-properties (id, total_amt, sync_token, customer_ref, private_note, payment_method_ref), so an agent inspecting the schema is not blind — the description just contributes nothing on top of it.

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 ('Update') and resource ('an existing payment') scoped to QuickBooks Online, so an agent knows exactly what entity is being modified. It does not, however, distinguish this from the many other update_* siblings (notably update_bill_payment), leaving resource selection to be inferred 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 guidance on when to use this versus create_payment, delete_payment, or update_bill_payment, and no stated preconditions. The one hint of a prerequisite — that the payment must already exist — is implicit in the word 'existing' rather than stated as a requirement.

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

Deploy Server