Skip to main content
Glama
justmytwospence

ynab-mcp

List Account Transactions

list_account_transactions
Read-only

Retrieve transaction history for a YNAB account to track spending, monitor cash flow, and analyze financial activity using date filters and categorization options.

Instructions

[1 API call] List transactions for a specific account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNoBudget ID or 'last-used'last-used
account_idYesThe account ID
since_dateNoOnly return transactions on or after this date (YYYY-MM-DD)
typeNoFilter by type
last_knowledge_of_serverNoDelta request token

Implementation Reference

  • The tool 'list_account_transactions' is registered and implemented in src/tools/transactions.ts. It calls the YNAB client's 'getTransactionsByAccount' method.
    server.registerTool("list_account_transactions", {
      title: "List Account Transactions",
      description: "[1 API call] List transactions for a specific account",
      inputSchema: {
        budget_id: z.string().default("last-used").describe("Budget ID or 'last-used'"),
        account_id: z.string().describe("The account ID"),
        since_date: z.string().optional().describe("Only return transactions on or after this date (YYYY-MM-DD)"),
        type: z.enum(TRANSACTION_TYPES).optional().describe("Filter by type"),
        last_knowledge_of_server: z.number().optional().describe("Delta request token"),
      },
      annotations: { readOnlyHint: true },
    }, async ({ budget_id, account_id, since_date, type, last_knowledge_of_server }) => {
      try {
        const response = await getClient().transactions.getTransactionsByAccount(
          budget_id, account_id, since_date, type, last_knowledge_of_server
        );
        const txns = response.data.transactions;
        if (txns.length === 0) return textResult("No transactions found for this account.");
        const lines = txns.map(formatTransaction);
        return textResult(`Account Transactions (${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 'readOnlyHint: true' already indicates this is a safe read operation. The description adds minimal context with '[1 API call]', hinting at performance or rate limits, but does not elaborate on pagination, return format, or other behavioral traits. It does not contradict annotations.

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 two short phrases, front-loaded with the key action and resource. There is no wasted verbiage, making it efficient and easy to parse.

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?

Given the read-only annotation and full schema coverage, the description is minimally adequate. However, without an output schema, it does not explain return values or format, and it lacks usage differentiation from siblings, leaving gaps in context for an AI agent.

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 schema fully documents all 5 parameters. The description mentions 'specific account' and 'list transactions', which aligns with the schema but adds no additional meaning beyond it. Baseline 3 is appropriate as 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 verb ('List') and resource ('transactions for a specific account'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'list_transactions' or 'list_accounts', which could cause confusion about scope.

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 such as 'list_transactions' (which might list all transactions) or 'list_account_transactions' (which filters by account). It lacks explicit when/when-not instructions or named alternatives.

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