QuickBooks Online MCP Server

update_vendor_credit

Updates a QuickBooks Online vendor credit by ID and sync token. Providing line_items replaces all existing lines, so fetch the credit first to change a single line.

Instructions

Update a vendor credit in QuickBooks Online. Providing line_items REPLACES the entire line array (fetch the current vendor credit first if you only want to modify one line); lines support per-line tax_code_ref and class_ref like bills.

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_vendor_credit"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the destructive replacement behavior for line_items and advises a read-before-write workflow, but it does not mention sync_token conflicts, permission requirements, or what happens to omitted fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the core action before the critical replacement caveat. Every phrase adds operational value, with no redundant or filler wording.

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

Completeness3/5

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

For a nested mutation tool with no annotations and no output schema, the description covers the most dangerous semantic detail around line replacement. It is still incomplete regarding concurrency via sync_token, partial-update behavior for other fields, and expected response shape.

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?

The description adds meaningful semantics for line_items by emphasizing full replacement and the read-first pattern, and it calls out per-line tax_code_ref and class_ref usage. However, it does not explain the roles of id, sync_token, vendor_ref, private_note, or global_tax_calculation beyond what the schema already provides.

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 a vendor credit in QuickBooks Online.' This clearly identifies the operation and target entity. It does not explicitly differentiate from siblings like create_vendor_credit, get_vendor_credit, or update_bill, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an important usage rule: providing line_items replaces the entire line array, and it names the alternative workflow of fetching the current vendor credit first if only one line should be modified. It does not describe when to prefer this tool over sibling update tools or when not to use it, so it is clear but not exhaustive.

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

Deploy Server