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. These are raw bank-feed lines; for recorded income use list_income, and for invoices/quotes use list_invoices.

Input Schema

TableJSON 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, and the description adds valuable context: these are raw bank-feed lines, not normalized income records, and it lists the fields returned. This meaningfully enriches the agent's understanding beyond the annotation without contradicting it.

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?

Two sentences with no waste. The first sentence front-loads the resource and returned fields; the second sentence provides sibling routing. Every clause earns its place.

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 zero required params and no output schema, the description compensates by listing the returned fields, clarifying the raw bank-feed nature, and routing to relevant siblings. Combined with the schema's thorough param documentation, nothing essential is missing for correct invocation.

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 every parameter has detailed semantics including pagination, filtering before pagination, and inclusive date/amount behavior. The description adds no parameter-level details, so the baseline 3 is appropriate.

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 ('the business's bank/feed transactions'), enumerates the returned fields, and explicitly distinguishes itself from siblings list_income and list_invoices. An agent can immediately tell what this tool returns and how it differs from nearby alternatives.

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?

Explicitly says these are raw bank-feed lines and directs the agent to list_income for recorded income and list_invoices for invoices/quotes. This gives clear when-to-use and when-not-to-use guidance with named alternatives.

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