Skip to main content
Glama

List transactions

list_transactions
Read-only

List the business's bank/feed transactions with signed amount, date, description, reference, running balance, linked income/expense ids and reconciliation status. Rows come newest first (by date, then id), 50 per page by default. When truncated is true there are older rows: pass the response's next_cursor back verbatim as cursor for the next page, or narrow with from/to. These are raw bank-feed lines; for recorded income use list_income, and for invoices/quotes use list_invoices.

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on/before this date (ISO 8601). Rows without a date are kept.
maxNoOnly rows whose amount is at most this (inclusive). Rows with no amount are excluded when min/max is set.
minNoOnly rows whose amount is at least this (inclusive). Rows with no amount are excluded when min/max is set. Applied before pagination.
fromNoOnly rows on/after this date (ISO 8601, e.g. "2026-01-01"). Rows without a date are kept.
limitNoMax rows to return in this page (default 50). Responses include next_cursor / truncated / total; pass next_cursor back as `cursor` to fetch the next page. Never silently truncated.
queryNoCase-insensitive substring filter — keeps only rows whose text (name, notes, and other string fields) contains this. Applied before pagination, so total/next_cursor reflect the filtered set.
cursorNoOpaque pagination cursor. Omit for the first page; pass the next_cursor from a previous response verbatim to fetch the next page.
bankaccountidNoOnly transactions on this bank account. Pass the bank account's id (as shown on a transaction's bank account, or in the business overview). Exact match; transactions with no bank account are excluded. Applied before pagination, so total/next_cursor reflect the filtered set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral context beyond that: sort order (newest first by date then id), default page size of 50, the meaning of truncated/next_cursor, and that filters apply before pagination. It does not mention auth requirements or rate limits, but for a read-only list tool this is solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with what the tool returns, followed by pagination mechanics and then the sibling routing. No filler; each sentence carries distinct information.

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?

There is no output schema, so the description correctly carries the return-shape burden by listing returned fields, ordering, and pagination signals. Combined with the routing guidance and the readOnlyHint annotation, an agent has everything needed to call and interpret this tool.

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%, so the schema already documents every parameter including from/to, min/max, query, cursor, limit and bankaccountid. The description only reiterates cursor/from/to usage without adding syntax or edge-case meaning beyond the schema, so the baseline of 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 (List) and resource (bank/feed transactions) and enumerates the returned fields (signed amount, date, reference, running balance, linked ids, reconciliation status). It explicitly differentiates from siblings by naming list_income and list_invoices as the tools for recorded income and invoices/quotes.

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?

Gives explicit routing: raw bank-feed lines here, list_income for recorded income, list_invoices for invoices/quotes. It also states the pagination workflow (check truncated, pass next_cursor back, or narrow with from/to), so the agent knows both when to use it and how to proceed when results are cut off.

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