Skip to main content
Glama

ynab_list_transactions

Read-onlyIdempotent

List and filter YNAB budget transactions by account, category, date, or status. Supports pagination for large result sets.

Instructions

List transactions for a budget with optional filtering and pagination.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • account_id (string, optional): Filter by account.

  • category_id (string, optional): Filter by category.

  • since_date (string, optional): ISO date (YYYY-MM-DD) to filter transactions on or after.

  • type (string, optional): "uncategorized" or "unapproved".

  • cleared (string, optional): "cleared", "uncleared", or "reconciled".

  • limit (int, optional): Max results per page. Default: 50.

  • offset (int, optional): Zero-based offset for pagination. Default: 0.

  • response_format (string, optional): "json" or "markdown" (default: "markdown").

Returns: transactions[], total_count, returned_count, offset, has_more, next_offset, cached, cache_info

Examples:

  • All transactions: call with no args (uses default budget)

  • Filter by account: set account_id

  • Last 30 days: set since_date to 30 days ago

  • Page 2: set limit=50, offset=50

Errors:

  • "No default budget set" → run ynab_set_default_budget first

  • Large result → use ynab_export_transactions to save to file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNo
offsetNo
clearedNo
budget_idNo
account_idNo
since_dateNo
category_idNo
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds details like pagination, caching (cached, cache_info), and error conditions (e.g., no default budget). It does not contradict 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 well-structured with clear sections (Args, Returns, Examples, Errors) and front-loaded with the purpose. It is somewhat lengthy due to 9 parameters, but each sentence adds value.

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 9 parameters, no required params, output schema presence, and no nested objects, the description covers all necessary aspects: optional params, pagination, error recovery, and alternative tools for large results. It is complete.

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?

Schema description coverage is 0%, but the description's 'Args' section explains every parameter in detail beyond the schema (e.g., defaults, format, behavior). For instance, it clarifies that budget_id is optional and defaults to the user's default budget.

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 the tool's purpose: list transactions for a budget with optional filtering and pagination. It distinguishes itself from sibling list tools by focusing on transactions and specifying filtering capabilities.

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 provides clear usage context, including examples and error handling (e.g., 'No default budget set' → run ynab_set_default_budget). It mentions alternatives for large results (ynab_export_transactions) but does not explicitly contrast with other transaction tools.

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/dizzlkheinz/ynab-mcpb'

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