QuickBooks Online MCP Server

search_purchases

Find QuickBooks Online purchases that match specified criteria, with filtering, sorting, and pagination options. Use it to locate transactions for review, reconciliation, or reporting.

Instructions

Search purchases in QuickBooks Online that match given criteria.

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

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 supplied, so the description carries the full behavioral burden, and it discloses almost nothing: 'Search' implies a non-destructive read but says nothing about permissions, result caps, pagination behavior, or how the criteria array is evaluated. For a query tool with seven nested sub-parameters, this is a substantial disclosure gap.

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?

It is a single front-loaded sentence with no filler, which is structurally fine. However, its brevity reflects under-specification rather than efficiency, since the one sentence omits nearly everything an agent needs.

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?

With no annotations, no output schema, and a nested parameter object with zero documented fields, the definition leaves the agent guessing about query syntax, pagination, and return shape. A criteria-based search tool needs at least a sketch of the criteria format and the paging model.

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 0%, and the description adds meaning for essentially one concept: 'criteria'. It says nothing about asc/desc, limit, offset, count, or fetchAll, so the agent has no idea what those nested fields do or how they interact.

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 states a specific verb and resource ('Search purchases') and scopes it to QuickBooks Online and 'given criteria', which is enough to distinguish it from get_purchase or create_purchase by name alone. It stops short of naming any sibling explicitly, so differentiation relies on the tool name rather than the prose.

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 this instead of get_purchase, search_purchase_orders, or the report tools, and no mention of prerequisites or typical query scenarios. The only hint is the word 'criteria', leaving the agent to infer everything about 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