YNAB MCP Server

List Scheduled Transactions

list_scheduled_transactions

Read-onlyIdempotent

List manually scheduled transactions in a YNAB budget to review upcoming planned payments; use transaction history or detect_recurring_charges for auto-imported recurring charges.

Instructions

List manually scheduled transactions only. For auto-imported recurring charges use transaction history or detect_recurring_charges.

Input Schema

Name	Required	Description
`budgetId`	No
`freshness`	No	fresh (default) reads YNAB. cached uses a session-isolated 30-second cache; complete means its reported coverage, which expands for older requested dates. Reports freshness; caller delta cursors bypass retention.
`projection`	No	Output fields: full (default) or lean IDs, values and essential status/link fields. Splits retain child IDs and amounts.
`includeFreshness`	No	Return an envelope with freshness/coverage metadata even on a fresh read.
`lastKnowledgeOfServer`	No	Delta cursor; returns { scheduled_transactions, server_knowledge }.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv6.1.0Oct 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / budgetId / description

Removed value: -"Budget ID (uses default if not provided)"

addedInput schema / properties / freshness

Added value: +{
+  "description": "fresh (default) reads YNAB. cached uses a session-isolated 30-second cache; complete means its reported coverage, which expands for older requested dates. Reports freshness; caller delta cursors bypass retention.",
+  "enum": [
+    "fresh",
+    "cached"
+  ],
+  "type": "string"
+}

addedInput schema / properties / includeFreshness

Added value: +{
+  "description": "Return an envelope with freshness/coverage metadata even on a fresh read.",
+  "type": "boolean"
+}

changedInput schema / properties / lastKnowledgeOfServer / description

Previous value: -"Delta request server knowledge. When provided, returns { scheduled_transactions, server_knowledge }."New value: +"Delta cursor; returns { scheduled_transactions, server_knowledge }."

addedInput schema / properties / projection

Added value: +{
+  "description": "Output fields: full (default) or lean IDs, values and essential status/link fields. Splits retain child IDs and amounts.",
+  "enum": [
+    "lean",
+    "full"
+  ],
+  "type": "string"
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedv5.4.0Sep 15, 2026
- removedOutput schema / properties / result / description
```
Removed value: -"Structured result returned by List Scheduled Transactions."
```

Changed1 schema field changedv5.1.1Jul 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "description": "Structured result returned by List Scheduled Transactions."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedv2.0.0May 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful data-scope caveat that only manual entries are returned, but says nothing about caching/freshness behavior or result size even though the schema exposes a freshness enum.

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?

Two sentences, both earning their place, with the scope restriction front-loaded and the routing hint immediately after. No restatement of the title or annotations.

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?

An output schema exists so return values needn't be explained, and the parameters are largely documented in the schema. What an agent still can't infer from the description is pagination or result-size behavior, but nothing essential to calling it correctly is missing.

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 80%, with freshness, projection, includeFreshness and lastKnowledgeOfServer all documented inline, including enums and the delta cursor shape. The description mentions no parameter semantics of its own, so the baseline 3 applies.

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?

States a specific verb and resource ('List ... scheduled transactions') plus a scope qualifier ('manually ... only'). It also names the sibling tools that cover the excluded case, so an agent can place it in the toolset without opening any schema.

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

Usage Guidelines4/5

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

Provides an explicit when-not rule and names the alternatives ('transaction history or detect_recurring_charges') for auto-imported recurring charges. It doesn't state prerequisites or whether budgetId is optional, but the routing guidance is clear.

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

Deploy Server