Skip to main content
Glama
pragprogrammer

YNAB MCP Server

create_scheduled_transaction

Schedule a future or recurring transaction in your YNAB budget. Specify account, amount, payee, category, and frequency to automate budgeting.

Instructions

Create a scheduled transaction (a transaction with a future date).

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) account_id: The account ID for this scheduled transaction date: Future date in YYYY-MM-DD format (no more than 5 years out) amount: Amount in dollars (negative for outflow, positive for inflow). e.g. -50.25 for spending $50.25 payee_id: Payee ID (use list_payees to find available IDs). For account transfers, use the target account's transfer_payee_id. payee_name: Payee name. If payee_id is null, this resolves to an existing payee or creates a new one. 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, description carries full burden. It discloses unsupported splits, date constraints, amount sign convention, payee fallback logic, category exclusions, memo length, flag colors, frequency values, and exclude_fields behavior. Lacks details on idempotency or side effects.

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?

Description is well-structured with a brief intro followed by parameter details. Slightly lengthy but every sentence adds value. Could be more concise by grouping related info.

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

Completeness5/5

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

Given complexity (11 params, 3 required, output schema exists), description provides thorough parameter guidance, key constraints, and unsupported features. Output schema covers return values. No gaps.

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 compensates. Each parameter gets detailed explanation: plan_id references list_plans, account_id, date format and constraint, amount sign meaning, payee_id references list_payees and transfer payee, payee_name fallback, category_id exclusion, memo max chars, flag_color enum, frequency enum, exclude_fields explanation.

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?

Description clearly states 'Create a scheduled transaction (a transaction with a future date)' with a specific verb and resource. It distinguishes from related tools like create_transaction (immediate) and list_scheduled_transactions.

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?

Description provides constraints (no splits, date must be future and within 5 years) but does not explicitly state when to use this tool versus alternatives like create_transaction. No when-not or alternative tool mentioned.

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