QuickBooks Online MCP Server

update_item

Modify an existing QuickBooks item by ID using a partial patch, so you can change only the fields that need updating without resending the full record.

Instructions

Update an existing item in Quickbooks by ID (sparse update).

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With zero annotations, the description carries the full behavioral burden and only supplies 'sparse update', which does usefully imply that unspecified fields are left untouched. It says nothing about required permissions, validation failures for an unknown item_id, whether omitted fields are cleared or preserved on nested sub-objects, or what the response contains.

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?

One short sentence, front-loaded with verb and resource, with no filler. It is efficient but leans toward under-specification rather than crisp brevity.

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?

For a mutation tool with no annotations, a nested/opaque schema at 0% coverage, and no output schema, the description is far too thin. An agent still lacks patchable field guidance, error/not-found behavior, and result shape — all of which the description would have to supply here.

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?

Schema coverage is 0% and the schema itself is opaque — an untyped `patch` object with additionalProperties {} and a bare `item_id` string. The description adds only that item_id identifies an existing record and that patch is sparse, but it never enumerates which item fields are patchable or what type each expects, so most parameter meaning is missing.

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+resource ('Update an existing item in Quickbooks') plus the lookup key (by ID) and the update mode (sparse). An agent can distinguish it from read_item/search_items/create_item/delete_item by the verb, though the description never names those siblings explicitly.

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/when-not guidance and no mention of alternatives such as search_items for finding the ID first or read_item for fetching current values. 'Sparse update' hints at partial-patch semantics but doesn't tell the agent when that is appropriate versus sending a full object.

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

Deploy Server