Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatescheduledtransaction

updateScheduledTransaction

Updates a scheduled transaction in a YNAB plan, allowing changes to its date, amount, payee, frequency, or other details.

Instructions

Updates a single scheduled 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>",
      "scheduled_transaction_id": "<scheduled_transaction_id>",
      "scheduled_transaction": "<scheduled_transaction>"
    },
    "name": "updateScheduledTransaction"
  }
}

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).
scheduled_transactionYes
scheduled_transaction_idYesThe id of the scheduled transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/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 discloses only that a mutation occurs. It does not say whether fields are merged or replaced (critical because the nested scheduled_transaction object has required fields), whether it requires authorization, or whether the operation is reversible.

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 short sentence contains no filler, so there is nothing to trim, but its brevity reflects under-specification rather than efficiency. It is front-loaded and readable, just nearly empty.

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

Completeness1/5

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

For a mutation tool with a nested object, three required parameters, no annotations, and no output schema, the definition provides no safety, permission, or update-semantics context. An agent could not confidently invoke this tool or predict its effect from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% and the key parameter is a nested object with required fields, so the description should clarify update semantics (partial vs full replacement). It adds nothing beyond the schema, leaving the most consequential ambiguity — whether omitted nested fields are preserved or cleared — unresolved.

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 sentence "Updates a single scheduled transaction" essentially restates the tool name and title. The only added token, "single", faintly distinguishes it from the bulk sibling updateTransactions, but the description makes no explicit differentiation or scope statement.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as updateTransactions (bulk) or createScheduledTransaction. The agent must infer the selection rules entirely from the tool name.

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