Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatetransaction

updateTransaction

Updates a single YNAB transaction by plan and transaction ID so you can change its date, amount, payee, category, memo, cleared status, approval, flag, or split details.

Instructions

Updates a single transaction

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": {
      "plan_id": "<plan_id>",
      "transaction_id": "<transaction_id>",
      "transaction": "<transaction>"
    },
    "name": "updateTransaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
transactionYes
transaction_idYesThe id of the transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / transaction / allOf
      Previous value: -[
      -  {
      -    "type": "object"
      -  },
      -  {
      -    "properties": {
      -      "account_id": {
      -        "format": "uuid",
      -        "type": "string"
      -      },
      -      "amount": {
      -        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      -        "format": "int64",
      -        "type": "integer"
      -      },
      -      "approved": {
      -        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      -        "type": "boolean"
      -      },
      -      "category_id": {
      -        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "cleared": {
      -        "description": "The cleared status of the transaction",
      -        "enum": [
      -          "cleared",
      -          "uncleared",
      -          "reconciled"
      -        ],
      -        "type": "string"
      -      },
      -      "date": {
      -        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      -        "format": "date",
      -        "type": "string"
      -      },
      -      "flag_color": {
      -        "description": "The transaction flag",
      -        "enum": [
      -          "red",
      -          "orange",
      -          "yellow",
      -          "green",
      -          "blue",
      -          "purple",
      -          "",
      -          null
      -        ],
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "memo": {
      -        "maxLength": 500,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_id": {
      -        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_name": {
      -        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      -        "maxLength": 200,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "subtransactions": {
      -        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.",
      -        "items": {
      -          "properties": {
      -            "amount": {
      -              "description": "The subtransaction amount in milliunits format.",
      -              "format": "int64",
      -              "type": "integer"
      -            },
      -            "category_id": {
      -              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "memo": {
      -              "maxLength": 500,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_id": {
      -              "description": "The payee for the subtransaction.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_name": {
      -              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      -              "maxLength": 200,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            }
      -          },
      -          "required": [
      -            "amount"
      -          ],
      -          "type": "object"
      -        },
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "account_id": {
      +        "format": "uuid",
      +        "type": "string"
      +      },
      +      "amount": {
      +        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      +        "format": "int64",
      +        "type": "integer"
      +      },
      +      "approved": {
      +        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      +        "type": "boolean"
      +      },
      +      "category_id": {
      +        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "cleared": {
      +        "description": "The cleared status of the transaction",
      +        "enum": [
      +          "cleared",
      +          "uncleared",
      +          "reconciled"
      +        ],
      +        "type": "string"
      +      },
      +      "date": {
      +        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      +        "format": "date",
      +        "type": "string"
      +      },
      +      "flag_color": {
      +        "description": "The transaction flag",
      +        "enum": [
      +          "red",
      +          "orange",
      +          "yellow",
      +          "green",
      +          "blue",
      +          "purple",
      +          "",
      +          null
      +        ],
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "memo": {
      +        "maxLength": 500,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_id": {
      +        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_name": {
      +        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      +        "maxLength": 200,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "subtransactions": {
      +        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split.",
      +        "items": {
      +          "properties": {
      +            "amount": {
      +              "description": "The subtransaction amount in milliunits format.",
      +              "format": "int64",
      +              "type": "integer"
      +            },
      +            "category_id": {
      +              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "memo": {
      +              "maxLength": 500,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_id": {
      +              "description": "The payee for the subtransaction.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_name": {
      +              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      +              "maxLength": 200,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "amount"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  2. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

"Updates" implies a mutation, but with no annotations the description does not disclose whether fields are partially replaced, which changes are ignored or rejected, or what side effects may occur. Important behaviors such as split-transaction restrictions, payee resolution or creation, and approval defaults appear only in the schema, not in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is readable and contains no filler, but its brevity is largely under-specification for a complex mutation. There is no structure or additional wording to surface the scope, alternatives, or operational constraints that matter when selecting the tool.

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

Completeness2/5

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

The rich schema supplies substantial field-level detail, but the definition lacks high-level selection guidance and a clear behavioral overview. With no annotations or output schema, the agent must closely inspect the nested schema to invoke the tool safely and cannot easily distinguish its intended use from sibling update operations.

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?

The description adds no parameter meaning beyond the input schema. The schema's 67% coverage and detailed field documentation make the tool minimally usable, including plan aliases, ISO dates, milliunits, and split constraints, but the description does not compensate for undocumented fields or clarify the overall transaction payload.

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

Purpose2/5

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

The description is understandable but essentially restates the name updateTransaction; "single" is the only meaningful scope added. It provides no YNAB/plan context, examples of updatable fields, or explicit differentiation from the sibling updateTransactions.

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?

There is no guidance about when to use this tool, when not to use it, or which alternative handles bulk updates, scheduled transactions, or other resources. "Single" weakly implies one-record usage, but no selection guidance or prerequisites are stated.

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