update_account
Update an existing chart-of-accounts entry. Code uniqueness is enforced.
What update_account does
Updates an existing account. Pass only the fields you want to change — every other field is preserved.
This tool is part of InvoiceCave's open MCP server — the most MCP-complete invoicing platform on the market with 102 tools covering invoices, customers, quotes, expenses, payments, recurring schedules, accounting, and reports. Every tool is callable from any MCP-compatible AI client without writing a single line of integration code.
How an AI uses update_account
Use this for partial edits — "change the due date to Net 30", "fix the customer's billing address", "update the line item description". The AI can read the current state with the matching get_* tool first if it needs to confirm what it's editing.
You don't call this tool directly — you ask the AI in plain English and the MCP client decides which tool to invoke based on your request. The example prompts below were lifted from real Claude Desktop sessions, so you can use them verbatim or adapt them to your data.
Parameters
update_account accepts 8 parameters — 1 required, 7 optional. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | required | Account ID |
| code | string | optional | — |
| name | string | optional | — |
| type | string | optional | — |
| subType | string | optional | — |
| description | string | optional | — |
| parentId | string | optional | — |
| isActive | boolean | optional | — |
Request example
Under the hood, your AI client sends a JSON-RPC 2.0 tools/call request to InvoiceCave's MCP endpoint at https://www.invoicecave.com/api/mcp/mcp. Here's what a update_account call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_account",
"arguments": {
"id": "id_a1b2c3d4",
"code": "example",
"name": "Acme Corp",
"type": "example",
"subType": "example"
}
}
}You won't write this yourself — it's shown so developers can see exactly what the MCP client generates. The arguments object maps 1:1 to the parameters above. Authentication is handled by the Authorization: Bearer header with your API key.
Example AI prompts
Type any of these into Claude Desktop, Claude Code, or Cursor — InvoiceCave's MCP server will route them to update_account automatically.
“Update this account — change the …”
“Fix the details on that account.”
Use it in 30 seconds
Related tools
More from the Chart of Accounts & Journals category.
list_accountsList chart of accounts. Optionally filter by type (Asset, Liability, Equity, Revenue, Expense).
list_journal_entriesList journal entries. Optionally filter by status (Draft, Posted, Void).
create_accountCreate a new account in the chart of accounts. Codes must be unique within the org.
delete_accountDelete an account. Fails if it has any journal lines — deactivate via update_account isActive=false instead.
seed_chart_of_accountsSeed the org with a standard 39-account chart of accounts (Assets/Liabilities/Equity/Revenue/Expense). Fails if any accounts already exist.
create_journal_entryCreate a journal entry. Validates double-entry (sum of debits must equal sum of credits). Pass status="Posted" to auto-post and update account balances; otherwise creates as Draft.
post_journal_entryPost a Draft journal entry. Updates affected account balances. Cannot be undone — to reverse, use void_journal_entry.
void_journal_entryVoid a journal entry. If it was Posted, account balances are reversed. Voided entries cannot be edited.
FAQ — update_account
What is update_account?▾
update_account is one of 102 tools in InvoiceCave's MCP server. Updates an existing account. Pass only the fields you want to change — every other field is preserved. It's invoked automatically when an AI client like Claude or Cursor decides the user's request maps to this action.
Which AI clients can call update_account?▾
Any MCP-compatible client. We've tested it with Claude Desktop, Claude Code, Cursor, Windsurf, and Codex. The MCP protocol is open, so any AI tool that speaks MCP can call this endpoint with a valid InvoiceCave API key.
Is calling update_account secure?▾
Yes. Every call is authenticated by the API key you mint in the dashboard, scoped to a single organization, rate-limited per key, and recorded in the audit log with source='mcp'. Sensitive fields (SMTP passwords, encryption keys) are never returned to the AI client.
What parameters does update_account take?▾
update_account accepts 8 parameters — 1 required (id) and 7 optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does update_account count against any quota?▾
MCP tool calls are unmetered on the free plan up to a generous monthly limit. Once you connect Stripe and start charging your customers, every call still counts against the same per-key rate limit but doesn't add to your bill.
Ready to wire this up?
Free plan — no credit card. 102 tools at your AI's disposal.