Skip to main content
Glama
calebl

YNAB MCP Server

by calebl

Update Transaction

ynab_update_transaction

Modify existing YNAB transactions by updating fields like amount, date, payee, category, or status to correct errors or reflect changes.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budgetIdNoThe ID of the budget (optional, defaults to YNAB_BUDGET_ID environment variable)
transactionIdYesThe ID of the transaction to update
accountIdNoMove transaction to a different account
dateNoThe date of the transaction in ISO format (e.g. 2024-03-24)
amountNoThe amount in dollars (e.g. -10.99 for outflow, 10.99 for inflow)
payeeIdNoThe ID of the payee
payeeNameNoThe name of the payee (creates new payee if doesn't exist)
categoryIdNoThe category ID for the transaction
memoNoA memo/note for the transaction
clearedNoThe cleared status
approvedNoWhether the transaction is approved
flagColorNoThe transaction flag color

Implementation Reference

  • The main handler function that performs the YNAB transaction update using the API, conditionally sets updatable fields, handles errors, and returns formatted response.
    export async function execute(input: UpdateTransactionInput, api: ynab.API) {
      try {
        const budgetId = getBudgetId(input.budgetId);
    
        // Build the update object with only provided fields
        const transactionUpdate: ynab.SaveTransactionWithOptionalFields = {};
    
        if (input.accountId !== undefined) {
          transactionUpdate.account_id = input.accountId;
        }
        if (input.date !== undefined) {
          transactionUpdate.date = input.date;
        }
        if (input.amount !== undefined) {
          transactionUpdate.amount = Math.round(input.amount * 1000);
        }
        if (input.payeeId !== undefined) {
          transactionUpdate.payee_id = input.payeeId;
        }
        if (input.payeeName !== undefined) {
          transactionUpdate.payee_name = input.payeeName;
        }
        if (input.categoryId !== undefined) {
          transactionUpdate.category_id = input.categoryId;
        }
        if (input.memo !== undefined) {
          transactionUpdate.memo = input.memo;
        }
        if (input.cleared !== undefined) {
          transactionUpdate.cleared = mapClearedStatus(input.cleared);
        }
        if (input.approved !== undefined) {
          transactionUpdate.approved = input.approved;
        }
        if (input.flagColor !== undefined) {
          transactionUpdate.flag_color = input.flagColor as ynab.TransactionFlagColor;
        }
    
        const response = await api.transactions.updateTransaction(
          budgetId,
          input.transactionId,
          { transaction: transactionUpdate }
        );
    
        if (!response.data.transaction) {
          throw new Error("Failed to update transaction - no transaction data returned");
        }
    
        const txn = response.data.transaction;
    
        return {
          content: [{
            type: "text" as const,
            text: JSON.stringify({
              success: true,
              transaction: {
                id: txn.id,
                date: txn.date,
                amount: (txn.amount / 1000).toFixed(2),
                payee_name: txn.payee_name,
                category_name: txn.category_name,
                memo: txn.memo,
                cleared: txn.cleared,
                approved: txn.approved,
                account_name: txn.account_name,
                flag_color: txn.flag_color,
              },
              message: "Transaction updated successfully",
            }, null, 2),
          }],
        };
      } catch (error) {
        console.error("Error updating transaction:", error);
        return {
          content: [{
            type: "text" as const,
            text: JSON.stringify({
              success: false,
              error: getErrorMessage(error),
            }, null, 2),
          }],
        };
      }
    }
  • Zod schema defining the input parameters for the tool, including descriptions.
    export const inputSchema = {
      budgetId: z.string().optional().describe("The ID of the budget (optional, defaults to YNAB_BUDGET_ID environment variable)"),
      transactionId: z.string().describe("The ID of the transaction to update"),
      accountId: z.string().optional().describe("Move transaction to a different account"),
      date: z.string().optional().describe("The date of the transaction in ISO format (e.g. 2024-03-24)"),
      amount: z.number().optional().describe("The amount in dollars (e.g. -10.99 for outflow, 10.99 for inflow)"),
      payeeId: z.string().optional().describe("The ID of the payee"),
      payeeName: z.string().optional().describe("The name of the payee (creates new payee if doesn't exist)"),
      categoryId: z.string().optional().describe("The category ID for the transaction"),
      memo: z.string().optional().describe("A memo/note for the transaction"),
      cleared: z.enum(["cleared", "uncleared", "reconciled"]).optional().describe("The cleared status"),
      approved: z.boolean().optional().describe("Whether the transaction is approved"),
      flagColor: z.enum(["red", "orange", "yellow", "green", "blue", "purple"]).optional().describe("The transaction flag color"),
    };
  • Exports the tool name and description for registration.
    export const name = "ynab_update_transaction";
    export const description = "Updates an existing transaction. All fields except transactionId are optional - only provide fields you want to change.";
  • Helper to retrieve or default the budget ID from input or environment.
    function getBudgetId(inputBudgetId?: string): string {
      const budgetId = inputBudgetId || process.env.YNAB_BUDGET_ID || "";
      if (!budgetId) {
        throw new Error("No budget ID provided. Please provide a budget ID or set the YNAB_BUDGET_ID environment variable.");
      }
      return budgetId;
    }
  • Helper to map string cleared status to YNAB enum.
    function mapClearedStatus(cleared: string): ynab.TransactionClearedStatus {
      switch (cleared) {
        case "cleared":
          return ynab.TransactionClearedStatus.Cleared;
        case "reconciled":
          return ynab.TransactionClearedStatus.Reconciled;
        default:
          return ynab.TransactionClearedStatus.Uncleared;
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, error handling, or response format. The optional field note is helpful but insufficient for a mutation tool with 12 parameters and no output schema.

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?

The description is a single, efficient sentence that front-loads the core action ('Updates an existing transaction') and adds a crucial behavioral note about optional fields. There is no wasted text, and it's structured to convey essential information concisely.

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?

Given the complexity of a mutation tool with 12 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), response expectations, and when to use versus siblings. While the schema covers parameters well, the description doesn't compensate for the gaps in broader context needed for safe and effective tool invocation.

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 100%, so the schema already documents all 12 parameters thoroughly. The description adds minimal value by noting that all fields except transactionId are optional, which clarifies the update semantics but doesn't provide additional syntax or format details beyond what the schema specifies. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the verb ('Updates') and resource ('an existing transaction'), making the purpose evident. It distinguishes from siblings like 'ynab_create_transaction' (create vs. update) and 'ynab_delete_transaction' (update vs. delete), but doesn't explicitly contrast with 'ynab_approve_transaction' which might overlap in functionality for approval status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for modifying existing transactions, but provides no explicit guidance on when to use this tool versus alternatives like 'ynab_approve_transaction' for approval changes or 'ynab_create_transaction' for new entries. It mentions that all fields except transactionId are optional, which offers some context for parameter usage, but lacks broader situational advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/calebl/ynab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server