Skip to main content
Glama
oliverames

YNAB MCP Server

Get Transactions

get_transactions
Read-onlyIdempotent

Retrieve YNAB transactions with optional filters by account, category, payee, month, or date range, and access raw merchant import names for payee disambiguation.

Instructions

Get transactions with optional filters. Use type='unapproved' or type='uncategorized' to filter. Optionally filter by account, category, payee, or month. You may combine one of accountId/categoryId/payeeId with month to fetch that resource's transactions for a specific month. Each returned transaction includes 'import_payee_name_original' — the raw merchant string from the bank import (e.g. 'AplPay LS ONION RIVEMONTPELIER VT') — which encodes processor flag, merchant name (often longer than the cleaned payee_name), and city+state. This is the primary disambiguation field when payee_name is truncated or ambiguous. YNAB now defaults omitted sinceDate to one year ago; pass an explicit older sinceDate to retrieve older history. Note: large date ranges (6+ months on a busy budget) can return 50KB+ of data; narrow with categoryId/payeeId/month/sinceDate/untilDate filters when possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by approval/categorization status
monthNoFilter by month (YYYY-MM-DD, first of month)
payeeIdNoFilter by payee ID
budgetIdNoBudget ID (uses default if not provided)
accountIdNoFilter by account ID
sinceDateNoOnly return transactions on or after this date (YYYY-MM-DD). If omitted, YNAB defaults to one year ago.
untilDateNoOnly return transactions on or before this date (YYYY-MM-DD)
categoryIdNoFilter by category ID
lastKnowledgeOfServerNoDelta request server knowledge. When provided, returns { transactions, server_knowledge }.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesStructured result returned by Get Transactions.
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds value by disclosing default sinceDate behavior, data size warnings, and the inclusion of 'import_payee_name_original' field with its raw merchant string details, providing behavioral context beyond annotations.

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

Conciseness4/5

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

The description is a single, dense paragraph that front-loads the main purpose and filters. Each sentence adds value without redundancy, but it could benefit from slight restructuring for readability. It is appropriately sized for the complexity.

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?

Given the tool's complexity (9 parameters, optional filters, filter combinations) and the existence of an output schema, the description is comprehensive. It covers filter strategies, default behavior, data volume warnings, and a critical field explanation, making it complete enough for effective tool usage.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds extra meaning by explaining filter combinations and default behaviors, such as the one-year default for sinceDate, and highlights the significance of a parameter field ('import_payee_name_original') not detailed in schema, enhancing semantic understanding.

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 'Get transactions with optional filters', specifying the resource (transactions) and action (get). It provides distinct filter types and a key field ('import_payee_name_original'), differentiating it effectively from singular get_transaction and list tools among siblings.

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?

The description gives clear guidance on filter combinations (e.g., combining accountId with month) and warns about large date ranges, but does not explicitly mention when to use alternative tools like get_transaction or search tools. It has clear context but lacks exclusions.

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/oliverames/ynab-mcp-server'

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