Skip to main content
Glama
johannesbraeunig

ynab-mcp

Create a YNAB transaction

ynab_create_transaction

Creates a single YNAB transaction using amount in milliunits, where negative values represent spending and positive values represent income.

Instructions

Create a single transaction. Amount is in milliunits: negative = outflow (spending), positive = inflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesISO 8601 date, e.g. 2026-07-01
memoNoTransaction memo
amountYesAmount in milliunits (1000 = 1.00 in the budget's currency). Positive = inflow, negative = outflow for transactions.
clearedNoDefaults to uncleared if omitted
approvedNoDefaults to false (unapproved) if omitted
payee_idNoExisting YNAB payee id
budget_idYesYNAB budget id, or "last-used" for the most recently used budget
account_idYesYNAB account id the transaction belongs to
payee_nameNoPayee name; YNAB creates a new payee if none matches. Ignored if payee_id is set.
category_idNoYNAB category id to assign
Behavior4/5

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

The description adds value beyond annotations by explaining the milliunits sign convention (negative=outflow, positive=inflow). Annotations already indicate non-read-only, non-idempotent, non-destructive behavior, so the description complements without contradiction. However, it could disclose more behavioral traits like duplicate handling.

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?

Two sentences, no redundancy. The critical detail about amount sign is front-loaded. Every sentence earns its place.

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 rich schema descriptions (100% coverage) and no output schema, the description is adequate. It covers the essential sign convention. Minor gap: no mention of the response (e.g., transaction object returned), but not required without output schema.

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 descriptions cover 100% of parameters, including the milliunits sign convention. The tool description repeats this information but does not add new meaning. Baseline score of 3 is appropriate per guidelines.

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 'Create a single transaction' with the verb 'Create' and resource 'a single transaction'. It distinguishes from sibling tools like 'ynab_create_transactions_bulk' (bulk) and 'ynab_update_transaction' (update). The addition about milliunits sign clarifies the tool's core behavior.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. It does not mention that for bulk creation, 'ynab_create_transactions_bulk' should be used, nor does it provide any prerequisites or context for 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/johannesbraeunig/ynab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server