list_transactions — Filtered, paginated transaction list

The list_transactions tool returns a filtered, paginated list of transactions for a single organization. Use it to build ledgers, reconcile activity, or search for specific payments. Every request must include intent and organizationId, and the token must carry the transactions.read scope. Results include cursor-based pagination.

Scope

Required OAuth scope: transactions.read

Input

string

required

The organization to query. Must be one of the organizations the token can access.

string

Filter to a single account.

string

Filter to a single card. When combined with accountId, both filters must match.

string

Filter by transaction status. Allowed values: created, processing, settled, returned, canceled, pending, unknown.

string

Filter by direction. Allowed values: debit, credit.

string

Free-text search across transaction fields. Must be 1 to 250 characters.

string

Inclusive lower bound. Accepts RFC 3339 timestamp or YYYY-MM-DD.

string

Inclusive upper bound. Accepts RFC 3339 timestamp or YYYY-MM-DD. When a date-only value is provided, the upper bound is the end of that day. The date window is rejected if inverted (after > before).

string

Opaque pagination cursor from a previous response. Keep the same pageSize and filters when following cursors. Never parse, edit, or reuse a cursor across different filter sets.

integer

default:"50"

Number of results per page. Must be between 1 and 100.

string

required

What the user asked for and why this call serves it, in 1 to 500 characters. Required on every tool call. See Common tool arguments.

Output

Transaction[]

required

Array of transactions matching the filters.

Show Transaction

string

required

Always "transaction".

string

required

Unique transaction identifier.

string

required

Organization the transaction belongs to.

string

required

Account the transaction belongs to.

string | null

required

Card associated with the transaction, if any.

Money

required

Unsigned amount as a Money object. Use direction for the sign.

string

required

Always "USD".

string

required

Sign carrier for the amount. Values: debit, credit.

string

required

Transaction lifecycle status. Values: created, processing, settled, returned, canceled, pending, unknown.

string

required

Payment rail. Values: ach, wire, card, check, transfer, fee, interest, other.

string

required

Human-readable description.

string

required

Name of the counterparty.

string

required

Category of the counterparty.

string

required

Timestamp when the transaction occurred, in RFC 3339 format.

object

required

Cursor-based pagination metadata.

Show Pagination

boolean

required

Whether more results are available.

integer

required

Number of results in this page.

string

Opaque cursor to fetch the next page. Present only when hasNextPage is true.

Example

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "list_transactions",
    "arguments": {
      "intent": "User asked for July debits on the Operating account; listing settled debits for that month.",
      "organizationId": "org_1",
      "accountId": "acc_1",
      "status": "settled",
      "direction": "debit",
      "occurredAfter": "2026-07-01",
      "occurredBefore": "2026-07-31",
      "pageSize": 10
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "structuredContent": {
      "data": [
        {
          "object": "transaction",
          "id": "txn_1",
          "organizationId": "org_1",
          "accountId": "acc_1",
          "cardId": null,
          "amount": { "cents": 12500, "display": "125.00", "currency": "USD" },
          "currency": "USD",
          "direction": "debit",
          "status": "settled",
          "type": "card",
          "description": "Coffee",
          "counterpartyName": "Blue Bottle",
          "counterpartyCategory": "restaurants",
          "occurredAt": "2026-07-01T14:03:00.000Z"
        }
      ],
      "pagination": {
        "hasNextPage": false,
        "pageSize": 10
      }
    }
  }
}

Notes

Follow nextCursor until hasNextPage is false. Keep the same pageSize and filters on every page.
Cursors are opaque and bound to the filter set. Never parse, edit, or reuse a cursor across different filters.
If an invalid cursor is supplied, the tool returns an MCP error: The pagination cursor is invalid. Restart pagination without a cursor and keep the same pageSize for subsequent pages.

get_transaction

Fetch a single transaction by ID.

Result conventions

Learn how pagination and dual-channel output work across all tools.

Organizations

Transactions

Accounts

Cards

Statements

Contacts

Catalog items

Invoices

list_transactions — Filtered, paginated transaction list

Scope

Input

Output

Example

Notes

get_transaction

Result conventions

​Scope

​Input

​Output

​Example

​Notes

get_transaction

Result conventions

Scope

Input

Output

Example

Notes