QuickBooks Online MCP Server

update_purchase_order

Modify an existing QuickBooks Online purchase order by ID and sync token to correct document details, vendor, or private notes.

Instructions

Update an existing purchase order 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_purchase_order"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.5/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. It does not mention the required sync_token optimistic-concurrency check, whether updates are partial or replace the whole record, whether fields can be cleared, or what happens on a stale token — all critical for a mutation tool.

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?

One efficient sentence with no filler, but its brevity is under-specification rather than conciseness — there is simply too little information for a mutation tool with an open-ended nested payload.

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 destructive mutation with zero annotations, no output schema, and a nested object accepting arbitrary additional properties, a single generic sentence is not sufficient. An agent cannot determine required permissions, side effects, or the role of sync_token from the definition 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?

The nested schema documents each field (id, sync_token, vendor_ref, doc_number, private_note), but the description adds no meaning beyond 'existing purchase order'. It explains nothing about whether vendor_ref changes re-price lines, whether omitted fields are preserved, or what additionalProperties allows in the untyped nested object.

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?

Clear verb plus resource ('Update an existing purchase order') and names the system (QuickBooks Online). It does not differentiate from the many sibling update tools (update_purchase, update_bill, update_vendor_credit), so it stops short of a 5.

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 guidance on when to use this versus update_purchase, update_bill, or search_purchase_orders; no prerequisites, no mention that the order must already exist and be in draft/open state. The only hint of usage is the word 'existing'.

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

Deploy Server