Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatetransactions

updateTransactions

Update multiple YNAB transactions by ID or import ID to correct dates, memos, amounts, payees, categories, cleared status, or approval state in one call.

Instructions

Updates multiple transactions, by id or import_id.

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>",
      "transactions": "<transactions>"
    },
    "name": "updateTransactions"
  }
}

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).
transactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / transactions / items / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "id": {
      -        "description": "If specified, this id will be used to lookup a transaction by its `id` for the purpose of updating the transaction itself. If not specified, an `import_id` should be supplied.",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "import_id": {
      -        "description": "If specified, this id will be used to lookup a transaction by its `import_id` for the purpose of updating the transaction itself. If not specified, an `id` should be supplied.  You may not provide both an `id` and an `import_id` and updating an `import_id` on an existing transaction is not allowed.",
      -        "maxLength": 36,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      }
      -    },
      -    "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: +[
      +  {
      +    "properties": {
      +      "id": {
      +        "description": "If specified, this id will be used to lookup a transaction by its `id` for the purpose of updating the transaction itself. If not specified, an `import_id` should be supplied.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "import_id": {
      +        "description": "If specified, this id will be used to lookup a transaction by its `import_id` for the purpose of updating the transaction itself. If not specified, an `id` should be supplied.  You may not provide both an `id` and an `import_id` and updating an `import_id` on an existing transaction is not allowed.",
      +        "maxLength": 36,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "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.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about permissions, whether the batch is atomic or can partially fail, or what happens when a supplied id does not resolve. The rich schema covers per-field constraints, but the description itself discloses no mutation behavior.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler; the lookup semantics are stated first. It is efficient, though the brevity reflects under-specification rather than disciplined concision.

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?

For an unannotated batch-mutation tool with no output schema, the description is far too thin: it omits partial-failure semantics, required permissions, and the relationship to updateTransaction. An agent could call it but cannot predict failure modes or results.

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 description coverage is 50% at the top level (plan_id documented, the transactions array undocumented), and the description's mention of `id`/`import_id` only restates what the schema already explains. It adds no meaning about the array, ordering, or size limits, so it neither compensates for the gap nor misleads.

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 and resource ("Updates multiple transactions") and adds the lookup key (id or import_id). The plural "multiple" implicitly distinguishes it from the singular updateTransaction sibling, but it never names that sibling explicitly.

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 on when to use this batch tool instead of the singular updateTransaction, no mention of preconditions (plan selection, auth), and no exclusions. The agent must infer usage purely from the word "multiple".

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