QuickBooks Online MCP Server

search_vendors

Find QuickBooks Online vendors by name, email, status, balance, or other fields. Apply filters and pagination to retrieve matching vendor records for AI-driven accounting workflows.

Instructions

Search vendors 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_vendors"
  }
}

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 must carry the behavioral burden. It says this is a search operation, but it does not disclose pagination behavior, default limits, what happens with empty criteria, fetchAll semantics, or authentication/rate-limit concerns.

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 a single front-loaded sentence with no wasted words. It is concise, though its brevity leaves important operational details unstated.

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 complex nested parameter object, no annotations, no output schema, and 0% schema description coverage, this description is far too thin. It identifies the basic purpose but lacks the operational guidance an agent needs to invoke it correctly.

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?

The description only mentions 'criteria' and says nothing about the other nested parameters such as asc, desc, count, limit, offset, or fetchAll. With schema description coverage at 0%, the description does not compensate for the schema's gaps.

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 and resource ('Search vendors') and adds the context ('QuickBooks Online') and condition ('match given criteria'). It is clear, but it does not explicitly differentiate the tool from sibling retrieval tools such as get-vendor.

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 sentence implies that the tool is for searching vendors, but it gives no explicit when-to-use guidance, no prerequisites, and no comparison to alternatives like get-vendor for retrieving a single vendor.

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

Deploy Server