QuickBooks Online MCP Server

report_item_sales

Generate a Sales by Product/Service Summary report to review item sales by date range, accounting method, grouping, and filters for customers, vendors, classes, or accounts.

Instructions

Run a Sales by Product/Service Summary report. Supports date range, accounting method, summarization, and filters.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.9/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 burden, and it discloses almost nothing behavioral. It does not confirm the tool is read-only, say whether the report is computed live or stored, describe the shape of the result, or mention any limits; only the parameter-level capabilities are hinted at.

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?

Two short sentences, front-loaded with the report name and followed by capability scope. Nothing is padded, though the second sentence is closer to a feature list than useful instruction.

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 nested-report tool with no output schema and no annotations, so the description should say more about what comes back and how the params object is structured. The rich nested schema compensates for much of the parameter side, leaving mainly the return-value and read-only questions unanswered.

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 context signal shows 0% schema description coverage, which reflects the undocumented top-level 'params' wrapper, but the nested filter properties (item, class, vendor, start_date/end_date vs date_macro, accounting_method, summarize_column_by) are themselves well described in the schema. The description only restates those categories ('date range, accounting method, summarization, and filters') without adding syntax, mutual-exclusion rules, or defaults.

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 and resource: 'Run a Sales by Product/Service Summary report.' That is concrete enough to distinguish it from generic reporting, though it never states how it differs from adjacent report siblings such as report_customer_sales, report_class_sales, or report_department_sales.

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 when-to-use or when-not-to-use guidance. 'Supports date range, accounting method, summarization, and filters' lists capabilities rather than telling an agent which of the many sibling sales/report tools to pick.

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

Deploy Server