QuickBooks Online MCP Server

report_journal

Generate a journal report with debit and credit detail for journal entries. Filter by date range, accounting method, account, class, or vendor; use 1–3 month ranges to avoid oversized responses.

Instructions

Run a Journal Report showing journal entries with debit/credit detail. WARNING: Large date ranges may produce very large responses — use 1-3 month ranges. Supports date range, accounting method, filters, and detail extras.

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": "report_journal"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose one important behavioral trait: large date ranges can produce very large responses. It does not explicitly state that the tool is read-only, nor does it describe permissions, response structure, or pagination behavior.

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?

The description is short and front-loads the purpose, followed by a useful warning and a brief capability summary. The phrase 'detail extras' is slightly vague, but overall there is little wasted text.

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?

This is a complex report tool with many nested parameters, no output schema, and no annotations. The description covers purpose, range caution, and broad capabilities, but it leaves gaps around read-only behavior and the shape of the returned report data.

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?

The nested schema already documents the available filters, date fields, columns, sorting, and accounting method in detail. The description adds only general capability language and the 1-3 month range advice, without adding meaning beyond the schema for individual parameters.

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: run a Journal Report showing journal entries with debit/credit detail. It is clear enough to distinguish this from journal-entry CRUD tools, but it does not explicitly differentiate itself from sibling reports such as report_general_ledger or report_transaction_list.

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 gives practical range guidance by warning that large date ranges may produce very large responses and recommending 1-3 month ranges. However, it does not explain when to choose this report over related reports or when to avoid it entirely.

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

Deploy Server