QuickBooks Online MCP Server

create_estimate

Create a QuickBooks Online estimate from a raw QBO Estimate object, including per-line tax codes for US or non-US companies.

Instructions

Create an estimate in QuickBooks Online. Accepts a raw QBO Estimate object; per-line tax codes go in Line[].SalesItemLineDetail.TaxCodeRef ({ value: } for non-US companies, 'TAX'/'NON' for US).

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It correctly implies a write/mutation and adds genuinely useful behavioral context that tax-code values are region-dependent (TaxCode Id for non-US vs 'TAX'/'NON' for US), but it omits required permissions, what happens to an estimate after creation (status, voiding/deletion via delete_estimate), failure modes, and return contents.

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?

Two sentences, front-loaded with the action and then the payload contract; no filler. The second sentence is dense with a nested path and parenthetical examples but every clause conveys operative information.

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?

Against a nested free-form payload with 0% schema coverage, no annotations, and no output schema, the description covers the tax-code gotcha well but leaves the agent guessing about mandatory fields (CustomerRef, Line), expected response, and error behavior. Adequate for a create tool, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'estimate' parameter is an untyped open object, so the description must compensate. It does so for exactly one path (Line[].SalesItemLineDetail.TaxCodeRef) and its region-dependent values, which is valuable, but the overall shape of the accepted QBO Estimate object remains undocumented in both schema and description.

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 an estimate in QuickBooks Online') and clarifies the input contract is a raw QBO Estimate object. It is clearly distinguishable from get_estimate, update_estimate, and search_estimates by the verb alone, though it never names the sibling it replaces or pairs with.

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?

No when-to-use guidance, no prerequisites (e.g., customer must exist, at least one Line required), and no mention of alternatives such as create_invoice for a finalized sale. The only guidance offered is about payload format, not about when this tool is the right choice.

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

Deploy Server