Skip to main content
Glama

Invio Xero MCP

list_xero_invoices

list_xero_invoices
Read-only

List invoices from Xero for the current organisation - sales invoices (ACCREC) or bills (ACCPAY), optionally filtered by status, by issue date range (fromDate/toDate, both inclusive), and by reference (exact match with reference, or a partial case-insensitive match with referenceContains - use exactly one, never both). Read-only; nothing is created, sent or changed. Each invoice carries its OWN currency straight from Xero - never assume it matches this user's Invio business currency. Returns up to 100 invoices for the requested page; if pageCount shows more pages than were returned, say so rather than implying this is the full list. The result always echoes back exactly which filters were applied (appliedFilters) - relay that, not just your own memory of what you asked for. Use get_xero_invoice for full line-item detail on one invoice.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number - Xero returns up to 100 invoices per page. Omit for page 1.
typeNoACCREC = sales invoices (money owed TO this business). ACCPAY = bills (money this business owes). Omit for both.
statusNoFilter to one Xero invoice status (e.g. AUTHORISED for approved-and-unpaid, PAID for settled). Omit for every status.
toDateNoOnly include records dated ON OR BEFORE this issue date, YYYY-MM-DD (inclusive - this IS the last date included, not the day after).
fromDateNoOnly include records dated ON OR AFTER this issue date, YYYY-MM-DD (inclusive). Filters on the issue Date, never the due date.
referenceNoExact match on the Reference field. Use this when you know the reference verbatim - cannot be combined with referenceContains.
organisationNoThe Xero organisation to use, by its display name. Only needed if this connection reaches more than one organisation - omit it when there is only one.
referenceContainsNoCase-insensitive PARTIAL match on the Reference field (e.g. "1234" matches a reference containing "PO-1234"). Use this when you only know part of the reference. Cannot be combined with reference - if you know the exact text, use reference instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / toDate / $ref
      Removed value: -"#/properties/fromDate"
    • addedInput schema / properties / toDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / toDate / type
      Added value: +"string"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds substantive behavior: a 100-per-page cap, pageCount-driven pagination meaning it is not necessarily the full list, and the appliedFilters echo that must be relayed rather than reconstructed. It also warns that each invoice carries its own Xero currency, which the annotations cannot convey. Only slight deduction for restating 'read-only; nothing is created' which the annotation already covers.

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?

One dense paragraph that front-loads the core purpose and document types before filters and caveats, with no filler sentences. It loses a point for duplicating schema-level guidance (reference vs referenceContains exclusivity) and for packing several agent-directed instructions into a single run-on block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With eight optional parameters and no output schema, the description carries the burden well: it describes the return shape (per-invoice currency, pageCount, appliedFilters) and the pagination ceiling, which is exactly what an agent needs to interpret results without an output schema.

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 100%, and the schema already documents inclusivity, the YYYY-MM-DD pattern, the mutual exclusivity of reference/referenceContains, and the organisation-omission rule. The description largely restates these rather than adding new meaning such as reference collation behavior or pageCount signaling thresholds, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list invoices from Xero) and immediately enumerates the two document families (ACCREC sales invoices vs ACCPAY bills), so an agent understands exactly what the result set contains. It also names the sibling get_xero_invoice as the detailed-single-record alternative, distinguishing itself without the schema being opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given: use get_xero_invoice for full line-item detail on one invoice. It also states the exclusive choice between reference and referenceContains ('use exactly one, never both') and the condition selecting each. Filter-omission semantics (omit status for every status, omit type for both) tell the agent when not to narrow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources