Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

get_transaction

Fetches full details for a YNAB transaction by ID, including date, payee, category, account, amount, memo, approval/cleared status, flag, and split allocations.

Instructions

Gets the full details of one transaction by ID: date, payee, category, account, amount, memo, approved/cleared status, and flag. Split transactions include a 'splits' array showing each portion's category and amount. Find transaction IDs with search_transactions or the list_* transaction tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transaction_id": "<transaction_id>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_idNoThe budget ID, or 'last-used' for the most recently used budget.last-used
transaction_idYesThe ID of the transaction to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; "Gets" implies a non-mutating read but does not state it, and nothing is said about behavior when an ID is invalid or not found. It does add genuine context by explaining that split transactions return a nested 'splits' array with per-portion category and amount.

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?

Front-loaded purpose followed by the returned-field inventory, the split-transaction caveat, and the ID-discovery hint. No sentence is filler and nothing important is buried.

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 simple two-parameter read tool with no output schema, the description covers what comes back and includes the important split-transaction shape. The only omission an agent might want is failure behavior for a bad transaction_id.

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% with both parameters documented inline, so the schema already carries the semantics. The description reinforces that transaction_id is the identifier and where to find it, while budget_id's 'last-used' default is left entirely to the schema.

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?

States a specific verb and resource ("Gets the full details of one transaction by ID") and enumerates the returned fields, so an agent can distinguish it from search_transactions or the list_* tools without opening a schema.

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?

Explicitly routes the agent to search_transactions or the list_* transaction tools to obtain IDs, which is the key prerequisite for calling this tool. It stops short of saying when to prefer this over search results, but the read-one-vs-find-many split is clear.

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