Skip to main content
Glama

ynab_create_transaction

Create a single transaction in YNAB by specifying account, amount, and date. Supports payee, category, memo, splits, and flags like cleared or approved.

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 (int, required): Amount in milliunits (dollars × 1000). Negative for expenses.

  • 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 accepts "amount" (integer milliunits), 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=-50000 (milliunits)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNo
account_idYes
amountYes
dateYes
payee_nameNo
payee_idNo
category_idNo
memoNo
clearedNo
approvedNo
flag_colorNo
import_idNo
dry_runNo
subtransactionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations indicate a non-read, non-destructive write operation. Description adds dry_run for preview and notes import_id behavior. Could elaborate on side effects like budget updates, but overall sufficient.

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?

Well-organized with clear sections (parameters, notes, examples). Slightly lengthy but every part is informative. Front-loads core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all 14 parameters, sibling tool differentiation, advanced usage, return value format, and example. Appropriate for a complex tool with nested subtransactions.

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 0% schema coverage, the description compensates fully by explaining each parameter's meaning, unit (milliunits), default values, and constraints (e.g., negative for expenses, cleared enum options).

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?

Clearly states 'Create a single transaction in YNAB', specifying verb and resource. Distinguishes from sibling tool ynab_create_receipt_split_transaction by contrasting use cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use this tool vs. the split-receipt version, provides details on optional vs required parameters, and includes an example. Also advises on the import_id field's role.

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