Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

edit_invoice

Modify existing invoices by updating date, due date, memo, customer, terms, email, payment settings, or invoice lines. Add or remove line items as needed.

Instructions

Modify an existing invoice. Can update date, due date, memo, customer, department, terms, email, online payment settings, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line (requires item_name), set delete=true to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInvoice ID to edit
txn_dateNoNew transaction date in YYYY-MM-DD format (optional)
due_dateNoNew due date in YYYY-MM-DD format (optional)
memoNoNew private memo (optional)
customer_memoNoNew customer-facing message visible on the invoice
bill_emailNoNew email address to send the invoice to
sales_term_refNoPayment terms name (e.g., 'Net 30'). Auto-resolved to ID.
allow_online_credit_card_paymentNoAllow customer to pay with credit card online
allow_online_ach_paymentNoAllow customer to pay via bank transfer (ACH) online
customer_nameNoNew customer display name (auto-resolved to ID)
department_nameNoHeader-level department/location name (auto-resolved to ID)
linesNoLine modifications. Provide line_id to update existing line, omit to add new line.
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?

No annotations provided, so description carries full burden. Lists modifiable fields and line operations, but omits side effects (e.g., whether totals recalculate, permissions needed) and fails to clearly state that draft=true means no save (default behavior is preview only).

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-sentence description is concise, front-loads purpose, and avoids redundancy. Each sentence adds distinct 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?

No output schema, but description does not mention return value or error handling. Covers main edit operations and line modifications, but missing key details about mutation effects and state changes.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). Description adds valuable context beyond schema for lines (update vs add vs delete) and draft behavior, justifying a higher score.

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?

Clearly states 'Modify an existing invoice' and enumerates specific fields that can be updated. Differentiates from create_invoice and other edit tools by scope, but does not explicitly exclude using for other invoice types.

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 basic guidance for lines (update/add/delete) but lacks explicit when-to-use or when-not-to-use compared to siblings like edit_bill or create_invoice. No alternatives mentioned.

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