Skip to main content
Glama
johannesbraeunig

ynab-mcp

List YNAB transactions

ynab_list_transactions
Read-onlyIdempotent

Retrieve transactions from a YNAB budget with date filtering and delta sync support to avoid re-fetching unchanged data.

Instructions

List transactions in a budget. Defaults to the last 30 days if since_date is not given, and returns at most 200 transactions per call (most recent first) with has_more indicating whether more exist for the window. Note: the YNAB API has no result-count limit of its own, so this tool always fetches every transaction in the requested date range before applying the 200-result cap — narrow the date range for large or long-lived budgets rather than requesting everything at once, both to keep the response small and to avoid burning YNAB's 200-requests/hour rate limit on an oversized fetch. For repeated polling of the same budget, prefer last_knowledge_of_server over re-fetching the full date range each time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idYesYNAB budget id, or "last-used" for the most recently used budget
since_dateNoOnly return transactions on or after this date. Defaults to 30 days ago. Must not be after until_date.
until_dateNoOnly return transactions on or before this date.
last_knowledge_of_serverNoDelta sync cursor: pass the server_knowledge value from a previous ynab_list_transactions call to receive only transactions that changed since then (ignores since_date/until_date filtering on the delta itself, though YNAB still applies them). Omit for a full fetch.
Behavior5/5

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

Beyond the annotations (read-only, idempotent, non-destructive), the description reveals critical behavioral traits: it fetches all results before applying the 200 cap, mentions the YNAB rate limit (200 requests/hour), and warns about potential heavy fetches. This adds significant value over the annotations alone.

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?

Five sentences, each providing essential information without repetition. The core purpose is front-loaded, followed by key behavioral details and usage guidance. No wasted words.

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?

Despite no output schema, the description covers return behavior (has_more, recent-first), pagination, defaults, rate limits, and delta sync. It fully addresses the complexity of a listing tool with multiple parameters and rate limit concerns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the schema already describes parameters. The description adds meaning beyond: it explains defaults (since_date defaults to 30 days ago), the behavior of last_knowledge_of_server (ignores date filters on delta but YNAB still applies them), and the interaction between parameters.

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?

The description clearly states 'List transactions in a budget,' using a specific verb and resource. It distinguishes from sibling list tools (e.g., list_accounts, list_budgets) by explicitly targeting transactions and adding contextual details about defaults and pagination.

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

Usage Guidelines4/5

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

Provides explicit guidance on default date range, result cap, pagination ('has_more'), and recommends narrowing date ranges for large budgets. It also suggests using 'last_knowledge_of_server' for polling to avoid rate limits. While it doesn't explicitly exclude sibling tools, the context makes its use clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johannesbraeunig/ynab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server