Skip to main content
Glama
alex1092

Up Banking MCP Server

up_list_transactions

Retrieve and filter banking transactions by account, date range, status, category, or tags to track spending and analyze financial activity.

Instructions

List transactions across all accounts or for a specific account. Supports filtering by status, date range, category, and tags. Returns paginated results ordered newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdNoOptional: Filter to transactions for a specific account
statusNoFilter by transaction status (pending or settled)
sinceNoStart date-time in RFC 3339 format (e.g., 2024-01-01T00:00:00+10:00)
untilNoEnd date-time in RFC 3339 format (e.g., 2024-12-31T23:59:59+10:00)
categoryNoFilter by category ID (e.g., 'restaurants-and-cafes', 'good-life')
tagNoFilter by transaction tag
pageSizeNoNumber of records to return (default: 30, max: 100)

Implementation Reference

  • MCP CallToolRequest handler case for 'up_list_transactions'. Extracts input arguments, calls the UpApiClient's listTransactions method, and returns the API response as formatted JSON text content.
    case "up_list_transactions": {
      const args = request.params.arguments as {
        accountId?: string;
        status?: "HELD" | "SETTLED";
        since?: string;
        until?: string;
        category?: string;
        tag?: string;
        pageSize?: number;
      };
      const result = await client.listTransactions(args);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Core helper function in UpApiClient that constructs the API endpoint and query parameters for listing transactions based on provided filters and invokes the generic makeRequest method to fetch data from Up API.
    async listTransactions(filters?: {
      accountId?: string;
      status?: "HELD" | "SETTLED";
      since?: string;
      until?: string;
      category?: string;
      tag?: string;
      pageSize?: number;
    }): Promise<{ data: TransactionResource[] }> {
      let endpoint = filters?.accountId
        ? `/accounts/${filters.accountId}/transactions`
        : "/transactions";
    
      const params = new URLSearchParams();
    
      if (filters?.status) {
        params.append("filter[status]", filters.status);
      }
      if (filters?.since) {
        params.append("filter[since]", filters.since);
      }
      if (filters?.until) {
        params.append("filter[until]", filters.until);
      }
      if (filters?.category) {
        params.append("filter[category]", filters.category);
      }
      if (filters?.tag) {
        params.append("filter[tag]", filters.tag);
      }
      if (filters?.pageSize) {
        params.append("page[size]", filters.pageSize.toString());
      }
    
      if (params.toString()) {
        endpoint += `?${params.toString()}`;
      }
    
      return this.makeRequest(endpoint);
    }
  • Input schema (JSON Schema) for the up_list_transactions tool, specifying the structure and descriptions of optional filter parameters.
      type: "object",
      properties: {
        accountId: {
          type: "string",
          description: "Optional: Filter to transactions for a specific account",
        },
        status: {
          type: "string",
          enum: ["HELD", "SETTLED"],
          description: "Filter by transaction status (pending or settled)",
        },
        since: {
          type: "string",
          description:
            "Start date-time in RFC 3339 format (e.g., 2024-01-01T00:00:00+10:00)",
        },
        until: {
          type: "string",
          description:
            "End date-time in RFC 3339 format (e.g., 2024-12-31T23:59:59+10:00)",
        },
        category: {
          type: "string",
          description:
            "Filter by category ID (e.g., 'restaurants-and-cafes', 'good-life')",
        },
        tag: {
          type: "string",
          description: "Filter by transaction tag",
        },
        pageSize: {
          type: "number",
          description: "Number of records to return (default: 30, max: 100)",
        },
      },
    },
  • src/index.ts:263-303 (registration)
    Tool definition object registered in the TOOLS array, used by ListToolsRequest handler to advertise the up_list_transactions tool with its name, description, and input schema.
      name: "up_list_transactions",
      description:
        "List transactions across all accounts or for a specific account. Supports filtering by status, date range, category, and tags. Returns paginated results ordered newest first.",
      inputSchema: {
        type: "object",
        properties: {
          accountId: {
            type: "string",
            description: "Optional: Filter to transactions for a specific account",
          },
          status: {
            type: "string",
            enum: ["HELD", "SETTLED"],
            description: "Filter by transaction status (pending or settled)",
          },
          since: {
            type: "string",
            description:
              "Start date-time in RFC 3339 format (e.g., 2024-01-01T00:00:00+10:00)",
          },
          until: {
            type: "string",
            description:
              "End date-time in RFC 3339 format (e.g., 2024-12-31T23:59:59+10:00)",
          },
          category: {
            type: "string",
            description:
              "Filter by category ID (e.g., 'restaurants-and-cafes', 'good-life')",
          },
          tag: {
            type: "string",
            description: "Filter by transaction tag",
          },
          pageSize: {
            type: "number",
            description: "Number of records to return (default: 30, max: 100)",
          },
        },
      },
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it lists transactions (read operation), supports filtering by multiple criteria, returns paginated results, and orders them newest first. This covers scope, output format, and ordering, though it doesn't mention rate limits, authentication needs, or error handling.

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 front-loaded with the core purpose in the first sentence, followed by filtering and pagination details in subsequent clauses. Every sentence adds value without redundancy, and it's appropriately sized for a tool with multiple parameters and no annotations. There's no wasted text.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is reasonably complete. It covers purpose, filtering scope, and output behavior (paginated, ordered). However, it lacks details on response format, error cases, or authentication requirements, which would be helpful for a list tool with many filters.

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?

The description adds some semantic context by listing filterable fields (status, date range, category, tags) and implying pagination, but the input schema already has 100% coverage with detailed descriptions for all 7 parameters. The description doesn't provide additional syntax, examples, or constraints beyond what's in the schema, so it meets the baseline for high schema coverage.

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 tool's purpose: 'List transactions across all accounts or for a specific account.' It specifies the verb ('List') and resource ('transactions'), and distinguishes it from siblings like 'up_get_transaction' (singular) and 'up_list_accounts' (different resource). However, it doesn't explicitly differentiate from 'up_get_account' or 'up_list_categories' beyond resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage context by mentioning filtering capabilities and pagination, but doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't clarify if this should be used over 'up_get_transaction' for single transactions or provide guidance on account-specific versus all-account queries. The context is clear but lacks explicit alternatives or exclusions.

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/alex1092/up-bank-mcp-server'

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