QuickBooks Online MCP Server

search_budgets

Search QuickBooks Online budgets by name, active status, and result limit to retrieve budget records with nested line-item details.

Instructions

Search for budgets in QuickBooks Online. Returns Budget records with nested BudgetDetail line items (Amount, BudgetDate, AccountRef, ClassRef, CustomerRef, DepartmentRef, LocationRef). Budget is read-only in the QBO v3 API.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully states that Budget is read-only in the QBO v3 API and describes the nested return structure, but it omits pagination behavior, default limits, permissions/auth requirements, and how filtering affects results.

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 definition is three sentences and front-loads the purpose before detailing return shape and read-only status. The list of nested BudgetDetail fields is somewhat dense, but it is relevant and does not bury the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with no annotations and no output schema, the description covers operation type and return composition. It is still incomplete about input filtering, pagination/default limit behavior, and how the nested params object should be used correctly.

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?

The description never mentions the input parameters or filters, despite the tool accepting name, limit, and active within a required params object. Given the reported 0% schema description coverage, the description should compensate for undocumented input semantics but does not.

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 opens with a specific verb and resource: 'Search for budgets in QuickBooks Online.' It also identifies the returned record type and nested BudgetDetail fields, so an agent knows exactly what operation is being performed and what kind of data comes back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The search framing implies this is the tool for retrieving or filtering budgets, and there is no sibling budget-lookup tool to differentiate from. However, it gives no explicit when-to-use guidance, no exclusions, and no explanation of when filtering by name/active/limit is appropriate.

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

Deploy Server