Skip to main content
Glama
calebl

YNAB MCP Server

by calebl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Transactions

ynab_get_transactions
Read-only

Retrieve YNAB transactions filtered by date range, account, category, payee, or approval status to analyze spending and manage budgets.

Instructions

Gets transactions from a plan with optional filters. Can filter by date range, account, category, payee, or approval status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by transaction type. Defaults to 'all'.
limitNoMaximum number of transactions to return (default: 100)
planIdNoThe plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)
payeeIdNoFilter to only transactions with this payee
budgetIdNoDeprecated alias of planId (still accepted)
accountIdNoFilter to only transactions in this account
sinceDateNoOnly return transactions on or after this date (ISO format: 2024-01-01)
categoryIdNoFilter to only transactions in this category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / anyOf
      Added value: +[
+  {
+    "description": "Filter to only transactions in this account",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / accountId / type
      Removed value: -"string"
    • addedInput schema / properties / budgetId / anyOf
      Added value: +[
+  {
+    "description": "Deprecated alias of planId (still accepted)",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / budgetId / description
      Previous value: -"The ID of the budget (optional, defaults to YNAB_BUDGET_ID environment variable)"New value: +"Deprecated alias of planId (still accepted)"
    • removedInput schema / properties / budgetId / type
      Removed value: -"string"
    • addedInput schema / properties / categoryId / anyOf
      Added value: +[
+  {
+    "description": "Filter to only transactions in this category",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / categoryId / type
      Removed value: -"string"
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "description": "Maximum number of transactions to return (default: 100)",
+    "exclusiveMinimum": 0,
+    "maximum": 1000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / limit / type
      Removed value: -"number"
    • addedInput schema / properties / payeeId / anyOf
      Added value: +[
+  {
+    "description": "Filter to only transactions with this payee",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / payeeId / type
      Removed value: -"string"
    • addedInput schema / properties / planId
      Added value: +{
+  "anyOf": [
+    {
+      "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The plan ID (optional, defaults to YNAB_PLAN_ID; budgetId is a deprecated alias)"
+}
    • addedInput schema / properties / sinceDate / anyOf
      Added value: +[
+  {
+    "description": "Only return transactions on or after this date (ISO format: 2024-01-01)",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / sinceDate / type
      Removed value: -"string"
    • addedInput schema / properties / type / anyOf
      Added value: +[
+  {
+    "description": "Filter by transaction type. Defaults to 'all'.",
+    "enum": [
+      "all",
+      "uncategorized",
+      "unapproved"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / type / enum
      Removed value: -[
-  "all",
-  "uncategorized",
-  "unapproved"
-]
    • removedInput schema / properties / type / type
      Removed value: -"string"
  2. Addedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already convey read-only and non-destructive behavior. The description adds only the existence of filters, not behavioral details such as default limit behavior, ordering, whether filters combine, or that unapproved transactions require a filter. No contradiction with annotations, but little added transparency.

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 short sentences with the core action front-loaded. No redundant or promotional language; every sentence contributes to understanding the tool.

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

Completeness3/5

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

For an 8-parameter tool with no output schema, the description is thin: it omits default behavior, return shape, and sibling-tool routing. However, the schema covers parameter formats and defaults, and annotations cover the safety profile, so the definition is minimally viable.

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 100%, so the baseline is 3. The description summarizes filter categories like date range and account, but does not add meaning beyond the schema's per-parameter descriptions.

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 ('Gets') and a concrete resource ('transactions from a plan'), then enumerates the supported filter dimensions. It is clearly understandable, but it does not explicitly distinguish itself from sibling tools like ynab_get_unapproved_transactions or ynab_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 Guidelines2/5

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

The description implies this is the general transaction-listing tool, but it gives no explicit guidance on when to choose it over alternatives. It does not mention exclusions or point to specialized siblings such as ynab_get_unapproved_transactions for unapproved-only queries.

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

Deploy Server

Other Tools