ynab-mcpb

Overview Schema Related Servers Score Discussions

ynab_update_transaction

Idempotent

Update an existing YNAB transaction by modifying its amount, date, payee, category, memo, or status. Preview changes with dry_run, then confirm to apply.

Instructions

Update fields on an existing YNAB transaction.

Args:

budget_id (string, optional): Budget UUID. Omit to use the default budget.
transaction_id (string, required): Transaction UUID to update.
amount_decimal (number, preferred): New amount in decimal currency units.
amount_milliunits (int, alternative): Explicit raw YNAB milliunits.
amount (int, deprecated): Backward-compatible alias for amount_milliunits.
date (string, optional): New date YYYY-MM-DD.
payee_name / payee_id (string, optional): New payee.
category_id (string, optional): New category UUID.
memo (string, optional): New memo.
cleared (string, optional): "cleared", "uncleared", or "reconciled".
approved (boolean, optional): Approval status.
dry_run (boolean, optional): Preview without saving.

Returns: updated transaction with updated_balance.

Write safety: call without confirmation_token to preview. Execute the identical validated request with the short-lived confirmation_token returned by that preview.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No
`memo`	No
`amount`	No	Deprecated legacy alias for amount_milliunits. Use amount_decimal for currency input or amount_milliunits for raw YNAB values.
`cleared`	No
`dry_run`	No
`approved`	No
`payee_id`	No
`budget_id`	No
`account_id`	No
`flag_color`	No
`payee_name`	No
`category_id`	No
`amount_decimal`	No	Preferred: amount in decimal currency units (for example, -12.34). Rounded exactly to the nearest YNAB milliunit.
`transaction_id`	Yes
`amount_milliunits`	No	Raw YNAB milliunits. Use only when the value is already converted.
`confirmation_token`	No	Short-lived, single-use token returned by the immediately preceding preview of this exact validated request.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Tool Definition Quality

A4.6/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description reveals a critical two-step workflow (preview then confirm) via confirmation_token and dry_run, and states it returns 'updated transaction with updated_balance', providing complete behavioral context.

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 a clear opening, a parameter list (though not formalized), and separate notes on returns and write safety. It is slightly verbose but front-loaded and every sentence adds value.

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?

Given 16 parameters and the presence of an output schema, the description covers the unique workflow, parameter guidance, and return value. It is sufficiently complete for an agent to use correctly, though it omits some parameter details like flag_color.

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?

With only 25% schema coverage, the description compensates thoroughly, explaining each parameter's role and preferences (e.g., amount_decimal is preferred, amount is deprecated), and clarifies the confirmation_token workflow, adding essential meaning beyond 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?

The description clearly states 'Update fields on an existing YNAB transaction', providing a specific verb (update) and resource (existing transaction), which distinguishes it from sibling tools like create, delete, or update multiple transactions.

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 includes explicit write safety instructions: preview without confirmation_token then execute with the token, but does not provide when-not-to-use or contrast with alternatives.

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

Install Server

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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