QuickBooks Online MCP Server

create_journal_entry

Create a journal entry in QuickBooks Online with debit/credit lines, transaction date, and line-level descriptions for accurate accounting records.

Instructions

Create a journal entry in QuickBooks Online. Description goes on the Line level, not inside JournalEntryLineDetail.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only states creation and a field-placement caveat. It does not disclose side effects, validation rules, balancing requirements, permission needs, or return behavior for this mutation tool.

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?

The description is two sentences, front-loaded with the core purpose, and the second sentence provides a specific implementation caveat. There is no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex nested mutation tool with no annotations and no output schema. The description covers only the basic action and one field-placement gotcha, leaving most of the schema complexity and behavioral expectations unaddressed.

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

Parameters2/5

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

The description adds one useful field-placement detail: Description must be at the Line level, not inside JournalEntryLineDetail. However, with 0% schema description coverage, it leaves key parameters such as required Line structure, TxnDate, PostingType, AccountRef, and debit/credit balancing unexplained.

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 states a specific verb and resource: 'Create a journal entry in QuickBooks Online.' This clearly identifies the operation, though it does not explicitly differentiate from sibling tools such as update_journal_entry or search_journal_entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only implies usage through the verb 'Create.'

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

Deploy Server