Skip to main content
Glama
calebl

YNAB MCP Server

by calebl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Transaction

ynab_update_transaction
Idempotent

Update an existing YNAB transaction by changing only the fields you specify, including split categories. Provide the transaction ID and new values for date, amount, payee, memo, or cleared status.

Instructions

Updates an existing transaction. All fields except transactionId are optional - only provide fields you want to change. Pass subtransactions to split an ordinary transaction across categories; YNAB cannot re-split a transaction that is already split.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe date of the transaction in ISO format (e.g. 2024-03-24)
memoNoA memo/note for the transaction
amountNoThe amount in dollars (e.g. -10.99 for outflow, 10.99 for inflow)
planIdNoThe plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)
clearedNoThe cleared status
payeeIdNoThe ID of the payee
approvedNoWhether the transaction is approved
budgetIdNoDeprecated alias of planId (still accepted)
accountIdNoMove transaction to a different account
flagColorNoThe transaction flag color, or an empty string to clear the flag
payeeNameNoThe name of the payee (creates new payee if doesn't exist)
categoryIdNoThe category ID for the transaction
transactionIdYesThe ID of the transaction to update
subtransactionsNoSplits an ordinary transaction across categories, in the same shape ynab_get_transactions returns. Needs at least two entries summing to amount (or the current amount if amount is omitted); omit categoryId. Not allowed on a transaction that is already split.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / subtransactions
      Added value: +{
+  "anyOf": [
+    {
+      "description": "Splits an ordinary transaction across categories, in the same shape ynab_get_transactions returns. Needs at least two entries summing to amount (or the current amount if amount is omitted); omit categoryId. Not allowed on a transaction that is already split.",
+      "items": {
+        "properties": {
+          "amount": {
+            "description": "The split amount in dollars, signed like the transaction amount",
+            "type": "number"
+          },
+          "category_name": {
+            "description": "The split's category name, matched loosely against your categories (optional)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "memo": {
+            "description": "A memo for this split (optional)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "payee_name": {
+            "description": "A payee for this split, if different from the transaction's (optional)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "amount"
+        ],
+        "type": "object"
+      },
+      "minItems": 2,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Splits an ordinary transaction across categories, in the same shape ynab_get_transactions returns. Needs at least two entries summing to amount (or the current amount if amount is omitted); omit categoryId. Not allowed on a transaction that is already split."
+}
  2. Changed28 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / anyOf
      Added value: +[
+  {
+    "description": "Move transaction to a different account",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / accountId / type
      Removed value: -"string"
    • addedInput schema / properties / amount / anyOf
      Added value: +[
+  {
+    "description": "The amount in dollars (e.g. -10.99 for outflow, 10.99 for inflow)",
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / amount / type
      Removed value: -"number"
    • addedInput schema / properties / approved / anyOf
      Added value: +[
+  {
+    "description": "Whether the transaction is approved",
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / approved / type
      Removed value: -"boolean"
    • addedInput schema / properties / budgetId / anyOf
      Added value: +[
+  {
+    "description": "Deprecated alias of planId (still accepted)",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / budgetId / description
      Previous value: -"The ID of the budget (optional, defaults to YNAB_BUDGET_ID environment variable)"New value: +"Deprecated alias of planId (still accepted)"
    • removedInput schema / properties / budgetId / type
      Removed value: -"string"
    • addedInput schema / properties / categoryId / anyOf
      Added value: +[
+  {
+    "description": "The category ID for the transaction",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / categoryId / type
      Removed value: -"string"
    • addedInput schema / properties / cleared / anyOf
      Added value: +[
+  {
+    "description": "The cleared status",
+    "enum": [
+      "cleared",
+      "uncleared",
+      "reconciled"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / cleared / enum
      Removed value: -[
-  "cleared",
-  "uncleared",
-  "reconciled"
-]
    • removedInput schema / properties / cleared / type
      Removed value: -"string"
    • addedInput schema / properties / date / anyOf
      Added value: +[
+  {
+    "description": "The date of the transaction in ISO format (e.g. 2024-03-24)",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / date / type
      Removed value: -"string"
    • addedInput schema / properties / flagColor / anyOf
      Added value: +[
+  {
+    "description": "The transaction flag color, or an empty string to clear the flag",
+    "enum": [
+      "red",
+      "orange",
+      "yellow",
+      "green",
+      "blue",
+      "purple",
+      ""
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / flagColor / description
      Previous value: -"The transaction flag color"New value: +"The transaction flag color, or an empty string to clear the flag"
    • removedInput schema / properties / flagColor / enum
      Removed value: -[
-  "red",
-  "orange",
-  "yellow",
-  "green",
-  "blue",
-  "purple"
-]
    • removedInput schema / properties / flagColor / type
      Removed value: -"string"
    • addedInput schema / properties / memo / anyOf
      Added value: +[
+  {
+    "description": "A memo/note for the transaction",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / memo / type
      Removed value: -"string"
    • addedInput schema / properties / payeeId / anyOf
      Added value: +[
+  {
+    "description": "The ID of the payee",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / payeeId / type
      Removed value: -"string"
    • addedInput schema / properties / payeeName / anyOf
      Added value: +[
+  {
+    "description": "The name of the payee (creates new payee if doesn't exist)",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / payeeName / type
      Removed value: -"string"
    • addedInput schema / properties / planId
      Added value: +{
+  "anyOf": [
+    {
+      "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)"
+}
  3. Addedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: patch semantics for omitted fields and the permanent restriction that YNAB cannot re-split an already-split transaction. It does not mention auth/permission requirements or error behavior on an invalid transactionId.

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 filler, and the most load-bearing fact (only transactionId required; only send what you want changed) is front-loaded ahead of the edge case about splitting.

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 mutation tool whose annotations already carry the safety profile and whose schema is fully documented, this covers the mutation model, the split workflow and its key limitation. Minor gaps remain around permissions and failure modes on a bad transactionId, but nothing essential to invoking it correctly is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents all 14 parameters including the split sub-shape. The description adds a usage rule the schema does not state plainly - supply only the fields you intend to change, and omit categoryId when passing subtransactions - which meaningfully affects how parameters are passed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Updates an existing transaction") and immediately clarifies the patch semantics, so an agent understands this is a partial mutation rather than a replace. It never names the sibling it is distinguished from (ynab_create_transaction, ynab_delete_transaction, ynab_approve_transaction), so it stops short of a 5.

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?

"All fields except transactionId are optional - only provide fields you want to change" gives clear when-to-use guidance for a patch tool, and the subtransactions sentence states the condition and the one hard exclusion (cannot re-split an already-split transaction). No explicit routing to alternative siblings (e.g. approve vs update), which keeps it below 5.

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

Deploy Server

Other Tools