Fetch QuickBooks Online account records in paginated batches. Control the number of results and starting position to navigate through your chart of accounts.
List Account records in QuickBooks Online with pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| maxResults | No | Maximum number of results to return (default: 100, max: 1000) | |
| startPosition | No | Starting position for pagination (1-based, default: 1) |
Changes observed during successful MCP inspections.
v1.6.2v1.6.0v1.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses the paginated behavior, which is a key trait, but doesn't mention whether the operation is read-only, auth requirements, or what happens with large result sets. For a simple list operation, this is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no redundancy. It is front-loaded with the verb and resource, and the pagination note is relevant. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with two self-explanatory parameters, the description adequately conveys the core functionality. It doesn't explain return values, but no output schema is present and the listing behavior is familiar. Minor gap: no mention of default limits beyond what the schema provides.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for both parameters (maxResults, startPosition), so the schema already explains their purpose. The description adds no additional parameter meaning, matching the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('List'), resource ('Account records'), and scope ('in QuickBooks Online'). It also mentions pagination, which distinguishes it from single-record retrieval (qbo_accounts_get) and filtered search (qbo_accounts_search).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like qbo_accounts_search or qbo_accounts_get. The description implies bulk retrieval via pagination but does not explicitly state use cases or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.