Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Gettransactionsbyaccount

getTransactionsByAccount

Retrieve non-pending transactions for a specific YNAB account, using date ranges and optional type filters to limit large results.

Instructions

Returns all transactions for a specified account, excluding any pending transactions

IMPORTANT: this can return thousands of transactions and overflow your context. Always pass since_date (and until_date when you know it) covering only the dates you need, such as the last 7 to 30 days. Without since_date, YNAB returns a full year. Pass type="unapproved" or type="uncategorized" when you only need those transactions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>",
      "account_id": "<account_id>"
    },
    "name": "getTransactionsByAccount"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoIf specified, only transactions of the specified type will be included. "uncategorized" and "unapproved" are currently supported.
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
account_idYesThe id of the account
since_dateNoIf specified, only transactions on or after this date will be included. The date should be ISO formatted (e.g. 2016-12-30). Defaults to one year ago when not specified.
until_dateNoIf specified, only transactions on or before this date will be included. The date should be ISO formatted (e.g. 2016-12-30).
last_knowledge_of_serverNoThe starting server knowledge. If provided, only entities that have changed since `last_knowledge_of_server` will be included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / since_date / description
      Previous value: -"If specified, only transactions on or after this date will be included.  The date should be ISO formatted (e.g. 2016-12-30)."New value: +"If specified, only transactions on or after this date will be included.  The date should be ISO formatted (e.g. 2016-12-30). Defaults to one year ago when not specified."
    • addedInput schema / properties / until_date
      Added value: +{
      +  "description": "If specified, only transactions on or before this date will be included.  The date should be ISO formatted (e.g. 2016-12-30).",
      +  "format": "date",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it warns the call can return thousands of records and overflow context, states the default one-year window when since_date is omitted, and notes pending transactions are excluded. It omits permission/auth requirements and pagination or response-shape behavior, keeping it from a 5.

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?

Front-loaded with the purpose and the critical warning; the IMPORTANT block is justified because the failure mode (context overflow) is real. Some phrasing could be tightened, but every sentence provides actionable information.

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?

For a six-parameter read tool with no annotations and no output schema, the description covers the main risks an agent needs: volume, default date window, pending-transaction exclusion, and filter usage. The remaining omission is the incremental-sync parameter, which the schema documents adequately on its own.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds practical meaning beyond the schema by explaining the consequence of omitting since_date (context overflow, full-year default) and when to apply the type filter. It says nothing about last_knowledge_of_server's incremental-sync use, leaving that parameter to the schema alone.

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?

States a specific verb and resource with scope ('all transactions for a specified account') plus an important exclusion ('excluding any pending transactions'). It doesn't explicitly contrast itself with the many sibling transaction tools (getTransactions, getTransactionsByMonth, getTransactionsByCategory), but the account-scoped nature is unambiguous from the name and description together.

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?

Gives concrete operational guidance: always pass since_date, add until_date when known, and use type filters when only unapproved/uncategorized transactions are needed. It lacks explicit routing to alternative sibling tools for other groupings, which is the only gap.

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