Skip to main content
Glama
pragprogrammer

YNAB MCP Server

update_scheduled_transaction

Update a scheduled transaction in YNAB by specifying account and future date, with optional changes to amount, payee, category, memo, flag color, or frequency.

Instructions

Update a scheduled transaction.

The API requires account_id and date on every update. Splits are not supported on this endpoint. Date must be in the future, no more than 5 years out.

Args: plan_id: The plan ID (use list_plans to find available IDs) scheduled_transaction_id: The scheduled transaction ID to update account_id: The account ID for this scheduled transaction (required) date: Future date in YYYY-MM-DD format (required, no more than 5 years out) amount: Amount in dollars (negative for outflow, positive for inflow) payee_id: Payee ID. For account transfers, use the target account's transfer_payee_id. payee_name: Payee name (resolves to existing or creates a new payee) category_id: Category ID. Credit Card Payment categories are not permitted. memo: Memo/note (max 500 chars) flag_color: 'red', 'orange', 'yellow', 'green', 'blue', 'purple', or null frequency: One of 'never', 'daily', 'weekly', 'everyOtherWeek', 'twiceAMonth', 'every4Weeks', 'monthly', 'everyOtherMonth', 'every3Months', 'every4Months', 'twiceAYear', 'yearly', 'everyOtherYear' exclude_fields: Optional list of field names to exclude from the response. If omitted, the model's default exclude list is used (see FIELDS.md). Pass [] to return all fields. Pass a custom list to override the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
memoNo
amountNo
plan_idYes
payee_idNo
frequencyNo
account_idYes
flag_colorNo
payee_nameNo
category_idNo
exclude_fieldsNo
scheduled_transaction_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, description carries full burden. Discloses split unsupported, future date limit, exclude_fields behavior. But missing idempotency, side effects, or behavior on already executed transactions.

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?

Well-structured with intro and Args list. Slight redundancy: 'requires account_id and date' mentioned twice. Otherwise efficient.

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 high parameter count, no annotations, and existing output schema, description covers constraints, parameter details, and behavioral notes. Lacks error handling or idempotency discussion, but sufficient for correct invocation.

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

Parameters5/5

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

Schema coverage is 0%, so description fully documents all 12 parameters with format, constraints, examples, and special cases (e.g., transfer_payee_id, negative amounts, flag colors, frequency options). No gaps.

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?

Clearly states 'Update a scheduled transaction' - specific verb and resource. Differentiates from siblings like create_scheduled_transaction, delete_scheduled_transaction, and get_scheduled_transaction.

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?

Provides key constraints (requires account_id and date, no splits, future date limited to 5 years) but lacks explicit when-to-use vs. alternatives like update_transaction or update_transactions. Does not mention prerequisites like plan_id validity.

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/pragprogrammer/mcp-ynab'

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