Skip to main content
Glama
justmytwospence

ynab-mcp

List Month Transactions

list_month_transactions
Read-only

Retrieve and filter transactions for a specific month from YNAB budgets to track spending, monitor categories, and review financial activity.

Instructions

[1 API call] List transactions for a specific month

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNoBudget ID or 'last-used'last-used
monthYesMonth in YYYY-MM-DD format (first of month)
since_dateNoOnly return transactions on or after this date
typeNoFilter by type
last_knowledge_of_serverNoDelta request token

Implementation Reference

  • Registration of the list_month_transactions tool.
    server.registerTool("list_month_transactions", {
      title: "List Month Transactions",
      description: "[1 API call] List transactions for a specific month",
      inputSchema: {
        budget_id: z.string().default("last-used").describe("Budget ID or 'last-used'"),
        month: z.string().describe("Month in YYYY-MM-DD format (first of month)"),
        since_date: z.string().optional().describe("Only return transactions on or after this date"),
        type: z.enum(TRANSACTION_TYPES).optional().describe("Filter by type"),
        last_knowledge_of_server: z.number().optional().describe("Delta request token"),
      },
      annotations: { readOnlyHint: true },
  • Handler implementation for the list_month_transactions tool.
    }, async ({ budget_id, month, since_date, type, last_knowledge_of_server }) => {
      try {
        const response = await getClient().transactions.getTransactionsByMonth(
          budget_id, month, since_date, type, last_knowledge_of_server
        );
        const txns = response.data.transactions;
        if (txns.length === 0) return textResult(`No transactions found for ${month}.`);
        const lines = txns.map(formatTransaction);
        return textResult(`Month Transactions for ${month} (${txns.length}):\n${lines.join("\n")}`);
      } catch (e: any) {
        return errorResult(e.message);
      }
    });
Behavior3/5

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

The annotation already declares readOnlyHint=true, so the agent knows this is a safe read operation. The description adds useful context about being a single API call, which hints at efficiency/rate limiting considerations. However, it doesn't describe pagination behavior, return format, or other behavioral traits beyond what annotations provide.

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?

The description is extremely concise with just two parts: the API call count and the core functionality. Every element earns its place, and it's front-loaded with the most important information (what the tool does).

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 a read-only tool with good schema coverage but no output schema, the description is minimally adequate. It states the core purpose but lacks important context about when to use it versus sibling tools, what the return format looks like, or any limitations beyond the single API call mention.

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 all parameters are documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('List transactions') and scope ('for a specific month'), which is a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'list_transactions' or 'list_account_transactions', which likely have overlapping functionality.

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 provides no guidance on when to use this tool versus alternatives like 'list_transactions' or 'list_account_transactions'. It mentions '[1 API call]' which hints at efficiency but doesn't explain when this specific month-focused tool is preferred over other listing tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/justmytwospence/ynab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server