QuickBooks Online MCP Server

create_item

Create a new item in QuickBooks Online to represent a product or service, specifying name, type, income account, and optional price and description.

Instructions

Create an item 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": "create_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.2/5.0

Behavior1/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 it discloses nothing beyond the name: no permission requirements, no note that item `type` governs which account refs are valid, no statement about duplicates or side effects on the chart of accounts, and no return information. Every behavioral fact an agent needs is absent.

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 front-loaded sentence with zero filler, which is structurally clean. However, the brevity is under-specification rather than conciseness — the sentence is too thin to be actionable for a create operation with a 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 mutation tool with no annotations, no output schema, a nested required object, and zero parameter documentation, the description should explain the type-dependent account references and success behavior. Nothing an agent needs in order to call this correctly is present.

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

Parameters1/5

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

Schema description coverage is 0% and the nested `params` object contains six undocumented fields, three of them required. The description does not explain what `type` accepts, what form an `income_account_ref` takes, or why `income_account_ref` is required while `expense_account_ref` is optional, so it compensates for none of the gap.

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 names a specific verb (Create) and resource (item) scoped to QuickBooks Online, so an agent knows exactly what object is produced. It does not distinguish this create from sibling lifecycle tools (read_item, update_item, delete_item, search_items) or note how it relates to creating related entities, but the resource noun makes the intent unambiguous.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. The agent gets no help deciding between create_item and the surrounding item/account tools, nor any indication of when this call would be inappropriate.

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

Deploy Server