QuickBooks Online MCP Server

search_purchase_orders

Search QuickBooks Online purchase orders by vendor and transaction date, with a limit on returned results. Use it to locate specific POs for review or reconciliation.

Instructions

Search for purchase orders 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": "search_purchase_orders"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and offers essentially nothing: no default page size or result cap, no note on whether matching is exact or fuzzy, no sorting behavior, and no indication of authorization or data scope. Only the product name is added context.

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 short, front-loaded sentence with no filler or redundancy. However, the brevity here reflects under-specification rather than disciplined economy.

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 search tool with a nested filter object, no annotations, and no output schema, the definition is too thin to guide correct use. Nothing describes what a result contains, how many are returned, or how paging works.

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 reported at 0% for the top-level wrapped params object, and the description adds nothing about the available filters (vendor_ref, txn_date_from, txn_date_to, limit) or the expected date format. The one sentence leaves the agent entirely dependent on the nested property names themselves.

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 ("Search for purchase orders") plus the system context (QuickBooks Online), so an agent knows what it looks up. It does not distinguish itself from siblings like get_purchase_order, search_purchases, or create_purchase_order, leaving the agent to infer the boundary.

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 mention of when to prefer get_purchase_order for a single record, and no indication of whether the search requires filters or can run bare. The agent must guess at the intended invocation context.

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

Deploy Server