Skip to main content
Glama

ynab_create_transaction

Create a single transaction in YNAB with support for splits, custom payees, and preview before saving.

Instructions

Create a single transaction in YNAB.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • account_id (string, required): Account UUID.

  • amount_decimal (number, preferred): Amount in decimal currency units (for example, -50.00). Negative for expenses.

  • amount_milliunits (int, alternative): Explicit raw YNAB milliunits (for example, -50000).

  • amount (int, deprecated): Backward-compatible alias for amount_milliunits. Values are never guessed by magnitude.

  • date (string, required): ISO date YYYY-MM-DD.

  • payee_name (string, optional): Payee name (creates new payee if not found).

  • payee_id (string, optional): Existing payee UUID (alternative to payee_name).

  • category_id (string, optional): Category UUID.

  • memo (string, optional): Memo text.

  • cleared (string, optional): "cleared", "uncleared", or "reconciled". Default: "uncleared".

  • approved (boolean, optional): Mark as approved. Default: false.

  • flag_color (string, optional): Transaction flag color ("red", "orange", "yellow", "green", "blue", "purple").

  • dry_run (boolean, optional): Preview without saving. Default: false.

  • subtransactions (array, optional): Manual split lines. Each entry uses exactly one of amount_decimal, amount_milliunits, or deprecated amount, plus optional "memo", "category_id", "payee_id", and "payee_name".

Use "subtransactions" for manual split transactions. Use "ynab_create_receipt_split_transaction" when you have itemized receipt data and want proportional tax allocation handled for you. Advanced: "import_id" is supported, but it is intentionally not part of normal guidance. Usually omit it if you want the transaction to remain eligible for later bank-import matching.

Returns: created transaction with account_balance.

Examples:

  • $50 expense: set amount_decimal=-50.00

  • Already-converted data: set amount_milliunits=-50000

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
NameRequiredDescriptionDefault
dateYes
memoNo
amountNoDeprecated legacy alias for amount_milliunits. Use amount_decimal for currency input or amount_milliunits for raw YNAB values.
clearedNo
dry_runNo
approvedNo
payee_idNo
budget_idNo
import_idNo
account_idYes
flag_colorNo
payee_nameNo
category_idNo
amount_decimalNoPreferred: amount in decimal currency units (for example, -12.34). Rounded exactly to the nearest YNAB milliunit.
subtransactionsNo
amount_milliunitsNoRaw YNAB milliunits. Use only when the value is already converted.
confirmation_tokenNoShort-lived, single-use token returned by the immediately preceding preview of this exact validated request.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations show readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds that the tool creates a transaction, supports a preview-with-execution flow, and returns account_balance. It also explains that import_id is intentionally omitted for normal use. No contradictions.

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 thorough but well-structured: a brief intro, a parameter list with clear formatting, usage notes, examples, and safety instructions. Every section adds value, though it could be slightly more concise by grouping related options.

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 the tool's complexity (17 parameters, multiple amount methods, splits, preview flow), the description covers the main use cases, safety, and alternatives. The output schema exists so return values are not needed. A few missing details (e.g., subtransaction max items) are minor.

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?

Schema coverage is low at 24%, but the description provides detailed explanations for each parameter including preferred amount methods, deprecation, subtransaction structure, and the confirmation_token flow. This adds significant semantics beyond the schema's minimal descriptions.

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 it creates a single transaction in YNAB. It distinguishes from the sibling tool for receipt splits and specifies the scope (single transaction, not batch or splits). The verb 'Create' and resource 'transaction' are precise.

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 says to use subtransactions for manual splits and references ynab_create_receipt_split_transaction for receipt data. Mentions write safety (preview with confirmation_token). However, it does not mention the batch sibling ynab_create_transactions for multiple transactions, missing a clear when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

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