QuickBooks Online MCP Server

search_transfers

Search QuickBooks Online transfers by date range and result limit to review account-to-account movements.

Instructions

Search for transfers in QuickBooks Online.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and falls well short: it does not say the operation is read-only, whether results are paginated, what the default limit is, or how date filters interact. Only the word 'Search' hints at non-destructive behavior.

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 single sentence is front-loaded and contains no filler, but its brevity reflects under-specification rather than efficiency. There is room for a second sentence on filtering and result limits without bloat.

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?

Given a nested parameter object, zero annotation coverage, no output schema, and a large family of sibling search tools, this description is far too thin. An agent cannot determine filtering syntax, pagination behavior, or result shape from it.

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?

Schema description coverage is 0% and the description adds nothing about the nested params object, the limit field, or the txn_date_from/txn_date_to filters. The property names are semi-self-explanatory, but date format and limit defaults are left entirely unstated.

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 names a specific verb ('Search') and resource ('transfers') in QuickBooks Online, which is enough for an agent to know it retrieves transfer records rather than mutating them. It does not, however, distinguish this from sibling get_transfer/read-style tools or explain what a search returns versus a single-record fetch.

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 search_transfers versus get_transfer, search_deposits, search_payments, or other transaction search tools, and no stated preconditions. An agent must infer from the name alone that this is the list/filter entry point for transfers.

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

Deploy Server