Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_items_create

Create inventory, service, or non-inventory items in QuickBooks Online with customizable attributes like price, description, tax status, and account references.

Instructions

Create a new Item record in QuickBooks Online.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
NameYesItem name (required, must be unique)
TypeNoItem type: Inventory, NonInventory, or Service. Required on create unless QBO infers it.
TaxableNoWhether the item is taxable on sales
QtyOnHandNoInitial on-hand quantity (Inventory items only)
UnitPriceNoDefault sales price
DescriptionNoSales description
InvStartDateNoInventory start date (YYYY-MM-DD, Inventory items only)
PurchaseCostNoDefault purchase cost
PurchaseDescNoPurchase-side description
AssetAccountRefNoAsset account reference, required for Inventory items, e.g. {"value": "81"}
IncomeAccountRefNoIncome account reference, e.g. {"value": "79"} (required for Inventory and Service items)
ExpenseAccountRefNoExpense or COGS account reference, e.g. {"value": "80"} (required for Inventory and NonInventory items)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, required permissions, or constraints like uniqueness of the Name field. The minimal description fails to compensate for the missing annotations.

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?

The description is concise (one sentence, 8 words) and directly states the purpose. However, it is arguably too brief, missing important context that could be included without harming conciseness.

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?

Given the complexity of the tool (12 parameters, nested objects, no output schema), the description lacks essential context about return values, side effects, and when to use this tool among siblings. It is insufficient for an agent to fully understand the tool's behavior.

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 100%, so the schema adequately documents parameters. The description adds no extra meaning beyond the schema, achieving the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (create), resource (Item record), and platform (QuickBooks Online). Among sibling tools, this uniquely identifies it as the tool for creating items, distinguishing it from other create tools like qbo_accounts_create.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, conditions, or when to choose create over other operations like update or search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/qbo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server