QuickBooks Online MCP Server

search_journal_entries

Search QuickBooks Online journal entries by criteria to locate specific accounting records, with options to limit, paginate, sort, and fetch all matching results.

Instructions

Search journal entries in QuickBooks Online that match given criteria.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Since no annotations are provided, the description bears the full burden of behavioral disclosure. It does not specify any limitations on criteria complexity, typical response sizes, or if the 'search' operation is paginated or capped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is simple and non-repetitive, achieving a baseline level of conciseness. However, its simplicity reflects a lack of depth and doesn't help structure complex parameter usage.

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?

The tool definition is complex, involving multiple search filters and pagination controls. The description completely fails to address the complexity of the input parameters or the scope of the search functionality beyond a generic statement.

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

Parameters1/5

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

With 0% schema description coverage, the description must explain the utility of the numerous parameters like limit, offset, and criteria. It only mentions 'given criteria,' which is a minimal placeholder that adds almost zero semantic value over the schema structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Search'), the resource ('journal entries'), and the scope ('in QuickBooks Online'). This immediately sets it apart from other list/retrieve operations like 'get_journal_entry'.

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?

The description provides no guidance on when to use this tool versus similar searching or listing tools in the QuickBooks suite. It assumes the agent knows the difference between a broad search and a specific fetch.

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

Deploy Server