Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_transactions

Read-only

Search and filter YNAB transactions by date, account, category, payee, amount, text, or status, returning compact rows with inflow/outflow totals and split details.

Instructions

Search transactions (newest first) with filters for dates, account, category, payee, amount and text. Returns a page of compact rows plus inflow/outflow totals for all matches. Split transactions show their splits; when filtering by category or payee, matching split lines are returned individually.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ynab_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoCase-insensitive text to find in payee, memo or category.
limitNoMax rows to return.
monthNoRestrict to one month ('current', 'YYYY-MM'); sets the dates.
offsetNoRows to skip (use next_offset from a prior call).
statusNoOnly uncategorized or only unapproved transactions.
clearedNoFilter by cleared status.
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
payee_idNoOnly this payee (id from ynab_list_payees).
directionNoOnly money in (inflow) or money out (outflow).
account_idNoOnly this account (id from ynab_list_accounts).
max_amountNoMaximum absolute amount in currency units.
min_amountNoMinimum absolute amount in currency units, e.g. 100 = $100.
since_dateNoEarliest date (YYYY-MM-DD). Defaults to 30 days ago unless month is given.
until_dateNoLatest date (YYYY-MM-DD).
category_idNoOnly this category (id from ynab_list_categories).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context on top: newest-first ordering, paged return with offset continuation, and totals computed over ALL matches rather than just the returned page (a non-obvious semantic). It also discloses split-transaction expansion behavior, which an agent could not infer from the schema.

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 the verb and key ordering fact, then results, then the split-transaction edge case. No filler, and each sentence adds a distinct fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter filtered list tool with an output schema and full annotation coverage, the description covers purpose, result shape, and the main non-obvious edge case. Minor room remains around default date-window behavior and when to widen it, but that default is already stated in the schema.

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 every one of the 15 parameters is already documented with formats and defaults. The description's filter list (dates, account, category, payee, amount, text) mirrors the schema without adding syntax, unit, or precedence rules beyond it, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Search transactions") and immediately states ordering (newest first) and the filter dimensions available. An agent can distinguish it from ynab_get_transaction by the plural, filtered, paged nature of the call, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage context is implied through the enumerated filters and the note that split lines are returned individually when filtering by category or payee, which is genuinely useful selection logic. However, there is no explicit statement of when to prefer this over ynab_get_transaction or ynab_list_scheduled_transactions, and no exclusions.

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