DoubleData MCP

List invoices

list_invoices

Read-only

Retrieve an organization's invoices newest first, showing number, status, totals, amount due, and hosted payment link; paginate using the previous page's next cursor.

Instructions

List the organization's invoices newest first with number, status, totals, amount due and a hosted payment link. Paginate with starting_after (the next_cursor of the previous page).

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": "list_invoices"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`status`	No
`starting_after`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: ordering (newest first), the fields surfaced (number, status, totals, amount due, hosted payment link), and cursor-based pagination semantics. It does not describe pagination termination (has_more / next_cursor presence), which would be the key remaining behavioral detail.

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 tight sentences with the scope and returned fields front-loaded, followed by pagination mechanics. Every sentence earns its place, though the returned-field list is a slightly dense clause that could be structured more readably.

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?

With no output schema and 0% parameter descriptions, the description carries full burden. It partially compensates by naming returned fields and explaining the cursor, but it omits how pagination terminates and what the status filter actually does, leaving gaps an agent would hit on multi-page or filtered retrieval.

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?

Schema description coverage is 0%, so the description must compensate. It defines starting_after precisely (the next_cursor of the previous page), which is valuable, but leaves status (enum values are in the schema, but filter semantics are unstated) and limit (default 25, max 100 in schema) undiscussed.

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 states a specific verb and resource ('List the organization's invoices') with scope (organization-wide) and ordering (newest first). It does not explicitly distinguish itself from siblings like get_invoice, download_invoice, or download_all_invoices, so an agent must infer that this is the enumeration counterpart rather than a single-invoice fetch or bulk download.

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?

Pagination usage is clearly explained (use starting_after with the next_cursor of the previous page), which is genuinely actionable. However, there is no guidance on when to choose this tool over get_invoice or download_all_invoices, nor on when to apply the status filter versus listing everything.

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