Skip to main content
Glama
hs737

MCP Server for YNAB

by hs737

Transactions — List by payee

transactions_list_by_payee
Read-only

List transactions for one payee and filter by status, approval, manual entry, date, or minimum amount. Results are paginated and can return only chosen fields.

Instructions

[READ] List transactions for a specific payee. Amounts in milliunits. Returns a paginated envelope with items, count, has_more, and next_offset. limit defaults to 100 and cannot exceed 500. Filters applied before paging: cleared ('cleared', 'uncleared', 'reconciled'), approved (true/false), manual_only=true for transactions with no import_id (entered by hand), min_amount to keep only transactions whose absolute amount is at least that many milliunits. fields: name the columns you need and each item is projected down to them, which is where the size of a long list actually goes — fields=['id,date,amount,cleared,import_id,payee_name,memo'] is a fraction of the full row. id is always included, and an unknown name is refused with the list of valid ones. Fields that are null or empty are omitted from each item. A missing category_id therefore means the transaction is uncategorized, and a missing subtransactions list means it is not a split.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNo
fieldsNo
offsetNo
clearedNo
plan_idNo
approvedNo
payee_idYes
min_amountNo
since_dateNo
manual_onlyNo
last_knowledge_of_serverNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered; the description goes well beyond that with pagination envelope shape, the limit default of 100 and hard cap of 500, the 'filters applied before paging' ordering rule, and the null/empty-field omission semantics. It even resolves what a missing category_id or subtransactions list means.

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?

Front-loaded with the purpose, then the return envelope, then defaults and filters, then the projection mechanism — a sensible order. It is long and a couple of clauses (the milliunits aside, the fields example) sprawl, but nearly every sentence carries operational content.

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 12-parameter, 0%-coverage schema this is close to sufficient, and it explains the return envelope even though an output schema exists. The residual gap is the handful of undocumented filter parameters (plan_id, since_date, type, last_knowledge_of_server) that an agent would have to guess at.

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?

With 0% schema coverage across 12 parameters, the description carries the burden and does meaningfully document limit, cleared (with its enum values), approved, manual_only, min_amount, and fields plus the id-always-included rule. It leaves type, plan_id, since_date, and last_knowledge_of_server unexplained, so a few parameters remain opaque.

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?

Opens with an explicit verb+resource+scope: '[READ] List transactions for a specific payee.' The payee scoping distinguishes it cleanly from the sibling list tools (transactions_list_by_account, transactions_list_by_category, transactions_list_by_month), so an agent can route without opening schemas.

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?

The description tells you what the filters mean but never states when to reach for this tool versus transactions_list, transactions_list_by_account, or the triage_* tools. Usage is implied by the payee scoping rather than spelled out, and no exclusions or prerequisites are given.

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