Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

edit_customer

Update customer information, including name, contact, addresses, notes, tax status, and payment terms. Set inactive to deactivate customer.

Instructions

Modify an existing customer. Can update name, contact info, addresses, notes, taxable status, active status, hierarchy (parent/sub-customer), delivery method, and payment terms. Set active=false to deactivate (QuickBooks equivalent of delete).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCustomer ID to edit
display_nameNoNew display name (must be unique in QuickBooks)
given_nameNoNew first/given name
middle_nameNoNew middle name
family_nameNoNew last/family name
suffixNoNew name suffix
company_nameNoNew company name
emailNoNew primary email address
phoneNoNew primary phone number
mobileNoNew mobile phone number
bill_addressNoNew billing address
ship_addressNoNew shipping address
notesNoNew notes about the customer
taxableNoWhether the customer is taxable
activeNoSet to false to deactivate customer (QuickBooks equivalent of delete)
parent_refNoParent customer name or ID (makes this a sub-customer). Auto-resolved to ID.
jobNoMark as a job (tracks work for a parent customer)
bill_with_parentNoBill this sub-customer with its parent
preferred_delivery_methodNoHow invoices are delivered: Print, Email, or None
sales_term_refNoDefault payment terms name (e.g., 'Net 30'). Auto-resolved to ID.
draftNoIf true, validate and show preview without saving (default: true)
Behavior3/5

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

With no annotations, the description must cover behavior. It mentions auto-resolution for parent_ref and sales_term_ref, and draft mode validation, but lacks details on authentication, error states, or side effects beyond deactivation.

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?

Two sentences efficiently deliver purpose and key behavior. No wasted words; front-loaded with the main 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 the tool's complexity (21 params, nested objects, no output schema), the description covers core functionality but omits return value, error handling, and validation details. Draft mode is explained, which helps.

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%, so baseline is 3. The description adds a summary of updatable fields and clarifies active's deactivation effect, but mostly overlaps with schema descriptions.

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 clearly states the verb 'Modify' and the resource 'customer', listing specific fields. It distinguishes from siblings like create_customer and delete_entity, but could be more explicit about when to use this vs other edit tools.

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 description provides some context (e.g., deactivation via active=false) but no explicit when-to-use or when-not-to-use guidance. It doesn't mention alternatives like delete+recreate or when to use draft mode.

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