QuickBooks Desktop MCP

Overview Schema Source Related Servers Discussions Admin

qb_list_runs

Read-only

Lists recent server runs newest first, showing what each booked and in which company file so you can find one to inspect or revert, with partly reverted runs marked.

Instructions

Lists this server's recent runs (newest first) with what each booked and in which company file, so you can find a run to inspect or revert. Fully reverted runs are not listed; partly reverted ones are marked, and a damaged run log is reported instead of its bookings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qb_list_runs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses ordering (newest first), an exclusion rule (fully reverted runs hidden), a state marker (partly reverted), and an error-shape behavior (damaged log reported instead of bookings). That is substantive behavioral context an agent could not infer from annotations alone; only limits/pagination specifics are missing.

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?

Three compact clauses, front-loaded with what the tool returns, then the goal, then the edge-case semantics. No filler and nothing repeated from the title or schema.

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

Completeness4/5

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

With an output schema present, return-shape detail is unnecessary, and the description covers filtering and degraded-state behavior well. The only real gap is the undocumented 'limit' parameter, which is minor given the schema default.

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 single parameter 'limit' has zero schema description coverage and the description never mentions it, its default of 20, or any maximum. 'Recent runs' only vaguely implies a bounded result set; the agent gets no explicit guidance on how many runs are returned or how to widen the list.

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?

Names a specific verb and resource ('Lists this server's recent runs') plus what each entry contains (bookings and company file) and the downstream purpose (inspect or revert). This clearly separates it from qb_revert_run, the sibling that acts on a run, and from transaction-listing siblings.

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

Usage Guidelines4/5

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

The 'so you can find a run to inspect or revert' clause supplies a concrete use case and implicitly routes the agent to qb_revert_run afterwards. It does not state exclusions (e.g., where to go for run contents or transactions), so it falls short of explicit when-not guidance.

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