Retrieve QuickBooks Online payment term records with pagination. Specify maxResults and startPosition to navigate large term lists efficiently.
List Term 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.4.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose reading behavior. It does not indicate whether the list is ordered, if it includes all terms, or any restrictions. The description is silent on permissions and rate limits.
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, clear sentence with no redundancy. It is front-loaded but could be slightly expanded for clarity without sacrificing conciseness.
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?
Given no output schema, the description should explain what the response contains. It does not. Also, lacking details on sorting or default behavior, making it incomplete for a listing tool with no annotations.
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?
Schema coverage is 100%, so baseline is 3. The description adds context by saying 'with pagination', which relates to the parameters, but does not add meaning beyond the schema descriptions.
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 specifies the verb 'List' and the resource 'Term records' with pagination, distinguishing it from get, create, and update tools. However, it does not differentiate from sibling tool qbo_terms_search, which likely offers filtered listing.
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?
The description mentions pagination, implying use for large datasets, but provides no explicit guidance on when to use this tool versus qbo_terms_search or other list tools. No exclusions or context are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.