Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

list_unapproved_transactions

Lists unapproved YNAB transactions—including bank-imported items awaiting review—so you can identify and clear pending approvals. Shows split transaction details when applicable.

Instructions

Lists transactions that haven't been approved yet (typically bank-imported transactions awaiting review). This is separate from categorization — a transaction can be categorized but still unapproved. Split transactions include a 'splits' array showing each portion's category and amount.

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": "list_unapproved_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_idNoThe budget ID, or 'last-used' for the most recently used budget.last-used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. "Lists" makes the read-only nature apparent and the definition adds real value on domain semantics (a transaction can be categorized yet still unapproved) plus a return-shape detail about the 'splits' array, but it says nothing about ordering, pagination, result limits, or whether approval status changes are possible from here.

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 short sentences, front-loaded with the core purpose, then a disambiguation, then a return-shape note. Every sentence carries distinct information and there is no filler.

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 single-parameter, read-only list tool with no output schema, the definition covers purpose, the meaning of the filter, its distinction from a nearby concept, and one notable field in the results. It falls slightly short only on list behavior (ordering, volume, pagination) that an agent might want before calling.

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 coverage is 100% and the single budget_id parameter is fully documented in the schema, including the 'last-used' default, so the baseline of 3 applies. The description adds no information about the parameter and does not state that it is optional or which budget's unapproved items are returned by default.

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?

"Lists transactions that haven't been approved yet" gives a specific verb and resource, and the parenthetical clarifies what "unapproved" means (bank-imported, awaiting review). It conceptually separates itself from categorization tools, though it never names the closely related sibling list_uncategorized_transactions, so an agent must infer that distinction itself.

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 is implied rather than stated: the agent learns these are items awaiting review, which suggests a review/approval workflow, but there is no explicit when-to-use or when-not guidance and no alternative tool is named (e.g., list_uncategorized_transactions or search_transactions). The 'separate from categorization' note is a useful exclusion signal but is framed as semantics, not as routing guidance.

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