Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Gettransactionsbymonth

getTransactionsByMonth

Fetch all non-pending transactions for a given YNAB plan month, with optional date and status filters to narrow results and review budget activity.

Instructions

Returns all transactions for a specified month, 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>",
      "month": "<month>"
    },
    "name": "getTransactionsByMonth"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoIf specified, only transactions of the specified type will be included. "uncategorized" and "unapproved" are currently supported.
monthYesThe plan month in ISO format (e.g. 2016-12-01) ("current" can also be used to specify the current calendar month (UTC))
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).
since_dateNoIf specified, only transactions on or after this date will be included. The date should be ISO formatted (e.g. 2016-12-30).
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. Changed1 schema field changedv0.2.0
    • 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 supplied, the description carries the full burden and does meaningful work: it discloses that pending transactions are excluded, that the call can return thousands of records and overflow context, and that omitting since_date yields a full year of data. It omits return shape, pagination behavior, and any auth or rate-limit context.

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?

The core behavior is front-loaded in one sentence, followed by a clearly flagged IMPORTANT block that earns its emphasis given the context-overflow risk. Minor redundancy exists in restating the type enum values that the schema already documents.

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 output schema and no annotations, the description covers the highest-risk behaviors: volume, pending exclusion, and date narrowing. Remaining gaps (response structure, last_knowledge_of_server semantics) are handled by the fully documented input schema.

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 would be 3, but the description adds real meaning beyond the schema by explaining the consequence of omitting since_date (a full-year response) and by framing since_date/until_date as the mechanism for bounding response size. It says nothing about month's "current" shortcut or plan_id's "last-used"/"default" values, which the schema already covers.

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 states a specific verb and resource with scope: returns all transactions for a specified month, excluding pending ones. That is far clearer than the title. It does not, however, distinguish itself from siblings like getTransactionsByAccount, getTransactionsByCategory, or getTransactions, so an agent must infer the difference from the name alone.

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?

It gives explicit when-to guidance for parameter usage: always pass since_date (and until_date when known) covering only the needed dates, such as the last 7 to 30 days, and use type="unapproved"/"uncategorized" when only those are needed. It stops short of stating when to choose this tool over the sibling transaction-listing tools.

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