Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

create_customer

Create a customer or sub-customer in QuickBooks with name, contact, address, and hierarchy settings. Returns customer details and a link to view.

Instructions

Create a customer or sub-customer. Accepts name parts, contact info, addresses, and hierarchy settings. Use parent_ref to create sub-customers or jobs. Returns customer details and a link to view in QuickBooks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
display_nameYesPrimary display name (must be unique in QuickBooks)
given_nameNoFirst/given name (optional)
middle_nameNoMiddle name (optional)
family_nameNoLast/family name (optional)
suffixNoName suffix, e.g., 'Jr.' (optional)
company_nameNoCompany name (optional)
emailNoPrimary email address (optional)
phoneNoPrimary phone number (optional)
mobileNoMobile phone number (optional)
bill_addressNoBilling address (optional)
ship_addressNoShipping address (optional, same shape as bill_address)
notesNoNotes about the customer (optional)
taxableNoWhether the customer is taxable (optional)
parent_refNoParent customer name or ID to create a sub-customer or job. Will be looked up to get ID.
jobNoMark this customer as a job (default: false). Jobs track work for a parent customer.
bill_with_parentNoIf true, invoices for this sub-customer are billed to the parent (default: false)
preferred_delivery_methodNoHow invoices are delivered: Print, Email, or None
sales_term_refNoDefault payment terms name (e.g., 'Net 30'). Will be looked up to get ID.
draftNoIf true, validate and show preview without creating (default: true)
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions returns details and a link, but does not disclose behaviors like uniqueness enforcement, failure modes, authentication needs, or rate limits. The draft mode effect is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences efficiently covering purpose, inputs, and output. Front-loaded with 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?

Given 19 parameters and no output schema, description covers input types and return value but lacks edge cases (e.g., duplicate display_name, unresolved parent_ref, draft mode impact). Adequate but not thorough.

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 100% with descriptions for all parameters. Description adds grouping context ('name parts, contact info, addresses') and mentions parent_ref for sub-customers, but does not significantly surpass schema details.

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?

Description clearly states 'Create a customer or sub-customer' and specifies accepted inputs (name parts, contact info, addresses, hierarchy settings). It distinguishes from sibling tools like edit_customer by focusing on creation.

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?

Description implies usage for creation and sub-customers, but does not explicitly state when to use this tool versus alternatives (e.g., edit_customer for updates). No exclusion criteria provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laf-rge/quickbooks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server