QuickBooks Online MCP Server

create_purchase_order

Create a QuickBooks Online purchase order from vendor and line-item details to track committed purchases before billing or receiving.

Instructions

Create a 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": "create_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.6/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 behavioral burden and discloses almost nothing. It does not say whether the PO is created in draft/open status, whether line items affect inventory or accounting, what permissions are needed, or what happens on validation failure.

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?

The single sentence is front-loaded and free of padding, but it is concise to the point of under-specification rather than efficient communication. Nothing beyond the tool name is conveyed.

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 a nested params object, no annotations, and no output schema, the description is far too thin. An agent gets no help on required inputs, dependencies on other tools, or the result of the call.

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 description coverage is reported at 0% and the actual schema text is minimal ('Vendor ID', 'Line items'), while the nested line_items fields (qty, item_ref, unit_price) have no descriptions at all. The description adds no meaning about the params envelope, the required vendor_ref/line_items pairing, or expected ID formats.

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 and resource (create a purchase order) in a named system, so the action is unambiguous. It does not distinguish this from nearby siblings such as create_purchase, create-bill, or create_vendor_credit, which an agent must disambiguate on its own.

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 guidance on when to use a purchase order versus a bill or purchase, no mention of prerequisites such as an existing vendor or item, and no reference to sibling tools like search_vendors or read_item that supply the required refs.

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

Deploy Server