list_cards — Paginated cards for an organization

The list_cards tool returns a paginated list of cards for a single organization, including physical and virtual cards in any status. Use it to let your agent discover cards, check spending limits, and review expiration dates. The token must carry the cards.read scope and every request must include intent and organizationId.

Scope

Required OAuth scope: cards.read

Input

string

required

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

string

Opaque pagination cursor from a previous response. Keep the same pageSize 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

Card[]

required

Array of cards.

Show Card

string

required

Always "card".

string

required

Unique card identifier.

string

required

Organization the card belongs to.

string

required

Account the card is linked to.

string

Last four digits of the card number. May be absent. The full card number is never returned.

string

required

Display nickname of the card.

string

required

Card form factor. Values: physical, virtual.

string

required

Card category. Values: debit, credit.

string

required

Card status. Values: pending, active, inactive, terminated, locked, unlockInProgress. Terminated cards are listed like any other.

string

required

Name of the cardholder.

integer

required

Expiration month (1-12).

integer

required

Expiration year.

object

required

Spending limits as Money objects. Individual values may be null when no limit is set.

Show SpendingLimits

Money | null

Daily purchase limit.

Money | null

Daily ATM withdrawal limit.

Money | null

Monthly purchase limit.

string

required

Timestamp when the card was created, 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": 6,
  "method": "tools/call",
  "params": {
    "name": "list_cards",
    "arguments": {
      "intent": "User asked which cards are active and what their spending limits are.",
      "organizationId": "org_1",
      "pageSize": 10
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 6,
  "result": {
    "structuredContent": {
      "data": [
        {
          "object": "card",
          "id": "card_1",
          "organizationId": "org_1",
          "accountId": "acc_1",
          "last4": "4242",
          "nickname": "Marketing card",
          "type": "virtual",
          "category": "debit",
          "status": "active",
          "cardholderName": "Jane Doe",
          "expMonth": 11,
          "expYear": 2028,
          "spendingLimits": {
            "dailyPurchase": { "cents": 500000, "display": "5,000.00", "currency": "USD" },
            "dailyAtmWithdrawal": { "cents": 100000, "display": "1,000.00", "currency": "USD" },
            "monthlyPurchase": { "cents": 5000000, "display": "50,000.00", "currency": "USD" }
          },
          "createdAt": "2026-01-04T00:00:00.000Z"
        }
      ],
      "pagination": {
        "hasNextPage": false,
        "pageSize": 10
      }
    }
  }
}

Notes

The last4 field may be absent. The full card number is never returned.
Terminated cards are listed like any other. Filter by status in your agent logic if you need to exclude them.
spendingLimits values are Money objects and may be null.
Follow nextCursor until hasNextPage is false. Keep the same pageSize on every page.
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_card

Fetch a single card 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_cards — Paginated cards for an organization

Scope

Input

Output

Example

Notes

get_card

Result conventions

​Scope

​Input

​Output

​Example

​Notes

get_card

Result conventions

Scope

Input

Output

Example

Notes