Skip to main content
Glama
QuickBooks Online MCP Server

QuickBooks Online MCP Server

by NightSquawk

report_profit_and_loss_detail

Generate a detailed Profit and Loss report with individual transactions; apply date ranges, filters, accounting method, and summarization to analyze financial activity.

Instructions

Run a detailed Profit and Loss report showing individual transactions. WARNING: Large date ranges may produce very large responses — use 1-3 month ranges. Supports date range, accounting method, summarization, 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_profit_and_loss_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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; it does disclose one real behavioral trait — response size scales with the date range and can become very large, with a recommended range. It omits other behavioral facts an agent would want, such as whether results are paginated or truncated and what the response structure looks like.

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?

Three short sentences, front-loaded with the purpose and immediately followed by the high-value warning about response size. No filler, though the trailing 'supports ...' sentence is largely a restatement of the schema and earns less place than the rest.

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?

For a report tool with a deeply nested filter schema and no output schema, the definition covers purpose and the main operational hazard but says nothing about return shape, row limits, or how summarization changes output. Adequate to invoke, not fully sufficient to predict results.

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 description enumerates parameter categories (date range, accounting method, summarization, filters, detail extras), which loosely maps to the nested params object. It adds no meaning beyond that — it does not mention date_macro, columns, sort_by/sort_order, or the start/end date exclusivity rule, all of which are already documented in the nested schema property descriptions.

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?

States a specific verb and resource ('Run a detailed Profit and Loss report') and narrows the scope with 'showing individual transactions', which implicitly separates it from the sibling report_profit_and_loss summary variant. The distinction from that sibling is implied rather than named, so it stops short of a 5.

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?

Gives a concrete operational constraint ('use 1-3 month ranges') that tells the agent how to call it safely. It never says when to prefer this detail report over report_profit_and_loss or the other report_* siblings, so sibling routing is left to inference.

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

Deploy Server

Other Tools