QuickBooks Online MCP Server

create_customer

Create a customer record in QuickBooks Online from a QBO Customer object; include DisplayName and optional tax identifiers for non-US businesses. Returns masked tax IDs.

Instructions

Create a customer in QuickBooks Online. Accepts a raw QBO Customer object (DisplayName required). Tax info for non-US companies: set PrimaryTaxIdentifier to the customer's tax registration number (e.g. EU VAT number / CIF), and optionally Taxable (boolean) and DefaultTaxCodeRef ({ value: }) for their default sales tax code. Responses always return PrimaryTaxIdentifier masked.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose one important side effect — 'Responses always return PrimaryTaxIdentifier masked' — which is real behavioral value. But it omits permissions/scopes required, duplicate-name rejection behavior, and whether the call is non-idempotent on retry, which matter for a create mutation.

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?

Three sentences, front-loaded with the core operation and payload type before the conditional tax detail. Dense but every sentence carries information; the tax sentence is slightly packed but not padded.

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?

No output schema and no annotations mean the description must stand alone for a mutation tool with a free-form nested payload. It covers the essential gotchas (required field, masked tax identifier, non-US tax setup) but leaves out duplicate handling, permission requirements, and error/response shape, so an agent could still be surprised at call time.

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 description coverage is 0% and the single parameter is an unconstrained free-form nested object, so the description must compensate. It does add meaning by naming the object model (QBO Customer), the one required field (DisplayName), and three tax-related fields with a shape hint (DefaultTaxCodeRef { value: <TaxCode Id> }), but leaves the bulk of a large QBO entity undocumented.

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?

States a specific verb and resource ('Create a customer in QuickBooks Online') and immediately clarifies the payload contract ('raw QBO Customer object, DisplayName required'). Against siblings like update_customer, delete_customer, search_customers and get_customer, the operation is unambiguous without opening any schema.

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?

Provides conditional guidance for one scenario ('Tax info for non-US companies: set PrimaryTaxIdentifier...'), which is genuinely useful context an agent could not infer. However it never says when to prefer update_customer over create_customer, nor what to do about pre-existing customers/duplicate DisplayName values, so the when-not guidance is absent.

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

Deploy Server