ynab-mcpb

Overview Schema Source Related Servers Discussions Admin

ynab_list_scheduled_transactions

Read-onlyIdempotent

Retrieve scheduled transactions with pagination and delta caching, returning amounts in both decimal currency and explicit milliunits for budgeting and reconciliation.

Instructions

List scheduled transactions with delta caching and pagination. Amounts are returned in decimal currency and explicit milliunits.

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`budget_id`	No

Output Schema

Name	Required	Description	Default
`cached`	Yes
`offset`	Yes
`has_more`	Yes
`used_delta`	Yes
`next_offset`	Yes
`total_count`	Yes
`returned_count`	Yes
`scheduled_transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.31.0Oct 29, 2026

addedOutput schema / properties / scheduled_transactions / items / properties / amount / description
```
Added value: +"Amount in decimal currency units"
```
addedOutput schema / properties / scheduled_transactions / items / properties / amount_currency
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / amount_formatted
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / debt_transaction_type
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / flag_name
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / import_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / import_payee_name
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / import_payee_name_original
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / matched_transaction_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / parent_transaction_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / scheduled_transaction_id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / scheduled_transactions / items / properties / subtransactions

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "description": "Amount in decimal currency units",
+        "type": "number"
+      },
+      "amount_currency": {
+        "type": "number"
+      },
+      "amount_formatted": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "amount_milliunits": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "category_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "category_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "deleted": {
+        "type": "boolean"
+      },
+      "id": {
+        "type": "string"
+      },
+      "memo": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "payee_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "payee_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "scheduled_transaction_id": {
+        "type": "string"
+      },
+      "transaction_id": {
+        "type": "string"
+      },
+      "transfer_account_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "transfer_transaction_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "amount"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / scheduled_transactions / items / properties / transaction_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / transfer_account_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / scheduled_transactions / items / properties / transfer_transaction_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / scheduled_transactions / items / properties / type

Added value: +{
+  "enum": [
+    "transaction",
+    "subtransaction"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / scheduled_transactions / items / required

Previous value: -[
-  "id",
-  "date_first",
-  "date_next",
-  "frequency",
-  "amount",
-  "amount_milliunits",
-  "account_id",
-  "account_name",
-  "payee_id",
-  "payee_name",
-  "category_id",
-  "category_name",
-  "memo",
-  "flag_color",
-  "deleted"
-]New value: +[
+  "id",
+  "amount",
+  "deleted",
+  "account_id",
+  "date_first",
+  "date_next",
+  "frequency"
+]

Changed12 schema fields changedv0.29.1Oct 26, 2026
- removedOutput schema / properties / scheduled_transactions / items / properties / category_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / category_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scheduled_transactions / items / properties / category_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / category_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scheduled_transactions / items / properties / flag_color / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / flag_color / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scheduled_transactions / items / properties / memo / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / memo / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scheduled_transactions / items / properties / payee_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / payee_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scheduled_transactions / items / properties / payee_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scheduled_transactions / items / properties / payee_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv0.27.1Jul 12, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive. The description adds two useful behavioral facts: results are paginated and delta-cached, and amounts are returned in both decimal and milliunits. However, "delta caching" is never explained (no cache token parameter exists in the schema), leaving an unclear mechanism for the agent.

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?

Two tight sentences with the core action front-loaded and no filler. Slightly under-specified rather than bloated, but structurally efficient.

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?

For a three-parameter tool with 0% schema coverage, the description leaves key semantics unresolved: budget_id's role and whether it defaults, what delta caching means to the caller. The presence of an output schema excuses it from explaining return values, but parameter-level gaps remain significant.

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 0%, so the description carries the full burden for limit, offset, and budget_id, yet it explains none of them. "Pagination" only loosely hints at limit/offset, and the budget_id parameter — critical since no default budget behavior is stated — is entirely undocumented.

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 uses a specific verb and resource ("List scheduled transactions") that clearly separates it from the get/create/update/delete scheduled-transaction siblings. It does not explicitly name the single-record sibling (ynab_get_scheduled_transaction) as the alternative, so differentiation is inferable rather than stated.

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?

It mentions pagination and delta caching but never says when to use this versus ynab_get_scheduled_transaction or the general ynab_list_transactions. There is no guidance on preconditions, no exclusions, and no indication of what happens if budget_id is omitted.

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

Deploy Server