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 its ID, changing any combination of date, amount, payee, category, memo, cleared status, flag, or account. Provide only the fields to modify.

Instructions

Updates an existing transaction. All fields except transactionId are optional - only provide fields you want to change.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)"
+}
  2. Addedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that the operation is non-read-only and non-destructive. The description adds useful behavioral context beyond that: it is a partial update where omitted fields are left unchanged. There is no contradiction with the annotations.

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 focused sentences with no superfluous content. The core purpose is front-loaded, and the parameter guidance is stated immediately and clearly.

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 13 parameters, complete schema descriptions, and annotations covering idempotence and destructive behavior, the description is sufficiently complete. The only minor omission is the return value, but this is not critical for correct invocation of an update tool.

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 value beyond the schema by clarifying that all non-transactionId fields are optional and that only fields explicitly provided are changed, which prevents an agent from sending the entire object unnecessarily.

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 states a specific action ('Updates') and resource ('an existing transaction'), and the word 'existing' clearly distinguishes it from ynab_create_transaction and ynab_delete_transaction. It is unambiguous about what the tool does.

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?

The description provides clear context: use this to modify an existing transaction, and only send fields to change. It does not explicitly name alternatives or state when not to use it, but the partial-update guidance is practical and sufficient for selection.

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