Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

set_transaction_memo

Replace a transaction's memo with new text, or clear it by passing an empty string; to keep existing text, retrieve it first and include it in the new memo.

Instructions

Sets (replaces) the memo on a transaction. Pass an empty string to clear the memo. To keep an existing memo, look it up first with search_transactions and include it in the new text.

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>",
      "memo": "<memo>"
    },
    "name": "set_transaction_memo"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoYesThe new memo text (max 500 characters). Empty string clears it.
budget_idNoThe budget ID, or 'last-used' for the most recently used budget.last-used
transaction_idYesThe ID of the transaction to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the key destructive trait (replace-overwrite, not append) and the empty-string clearing behavior, which is exactly the data-loss risk an agent needs. It omits permissions, error modes, and whether the response echoes the updated transaction.

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?

Three short sentences, each carrying a distinct payload: what it sets, how to clear it, and how to avoid clobbering data. The replace semantics and clearing behavior are front-loaded before the workflow note.

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 3-parameter mutation with fully described schema and no output schema, the essentials are covered: overwrite semantics, clearing, and preservation workflow. The only unstated item is what the call returns or what happens on an invalid transaction_id, which is a modest omission given no output schema exists.

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 100%, so the baseline is 3; the description adds meaning beyond it by framing memo as a full replacement value and by implying the caller must supply the prior text rather than patching. It says nothing extra about budget_id, which the schema already documents with its 'last-used' default.

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 ('Sets (replaces) the memo on a transaction') and immediately disambiguates the mutation semantics as replacement rather than append. An agent knows exactly what changes and at what granularity without opening the 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?

Gives a concrete conditional workflow: if an existing memo must be preserved, look it up first with search_transactions and resend it. That names the alternative tool and the condition that selects it. It does not state when not to use the tool, but for a single-purpose setter that is a minor gap.

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