Skip to main content
Glama
iaptic

Iaptic MCP Server

Official
by iaptic

transaction_list

Retrieve paginated lists of financial transactions from your Iaptic account, filtered by date or purchase ID.

Instructions

List financial transactions from your Iaptic account.

  • Returns a paginated list of transactions

  • Use limit and offset for pagination (default: 100 per page)

  • Filter by date range using startdate and enddate (ISO format)

  • Filter by purchaseId to see transactions for a specific purchase

  • Results include transaction status, amount, currency, and payment details

  • Results are ordered by transaction date (newest first)

  • Important: Use date filtering to avoid retrieving too many records

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return (default: 100, max: 1000)
offsetNoNumber of transactions to skip for pagination
startdateNoFilter transactions after this date (ISO format, e.g. 2024-01-01)
enddateNoFilter transactions before this date (ISO format, e.g. 2024-12-31)
purchaseIdNoFilter transactions by purchase ID

Implementation Reference

  • Handler for 'transaction_list' tool. Calls this.api.getTransactions() with limit (capped at 1000), offset, startdate, enddate, purchaseId, and appName args, then returns the result as JSON text content.
    private async _handleTool(name: string, args: any) {
      switch (name) {
        case 'transaction_list':
          console.error(`Fetching transactions with params:`, args);
          const transactions = await this.api.getTransactions({
            limit: Math.min(args.limit || 100, 1000),  // Cap at 1000
            offset: args.offset,
            startdate: args.startdate,
            enddate: args.enddate,
            purchaseId: args.purchaseId,
            appName: args.appName
          });
          console.error(`Retrieved ${transactions.rows?.length || 0} transactions`);
          return {
            content: [{
              type: "text",
              text: JSON.stringify(transactions, null, 2)
            }]
          };
  • Input schema for 'transaction_list' tool. Defines parameters: limit (number, max 1000), offset (number), startdate (string, ISO format), enddate (string, ISO format), purchaseId (string), and optionally appName when using master key.
    inputSchema: {
      type: "object",
      properties: {
        limit: { 
          type: "number", 
          description: "Maximum number of transactions to return (default: 100, max: 1000)" 
        },
        offset: { 
          type: "number", 
          description: "Number of transactions to skip for pagination" 
        },
        startdate: { 
          type: "string", 
          description: "Filter transactions after this date (ISO format, e.g. 2024-01-01)" 
        },
        enddate: { 
          type: "string", 
          description: "Filter transactions before this date (ISO format, e.g. 2024-12-31)" 
        },
        purchaseId: { 
          type: "string", 
          description: "Filter transactions by purchase ID" 
        },
        ...(appNameRequired ? {
          appName: {
            type: "string",
            description: "Name of the app to fetch data from. Required when using master key."
          }
        } : {})
      },
      required: appNameRequired ? ["appName"] : undefined
    }
  • Registration of the 'transaction_list' tool with its name and description. Part of the array returned by TransactionTools.getTools().
          {
            name: "transaction_list",
            description: `List financial transactions from your Iaptic account.
    - Returns a paginated list of transactions
    - Use limit and offset for pagination (default: 100 per page)
    - Filter by date range using startdate and enddate (ISO format)
    - Filter by purchaseId to see transactions for a specific purchase
    - Results include transaction status, amount, currency, and payment details
    - Results are ordered by transaction date (newest first)
    - Important: Use date filtering to avoid retrieving too many records${appNameRequired ? '\n- Requires appName parameter when using master key' : ''}`,
  • src/server.ts:94-97 (registration)
    Routing of 'transaction_' prefixed tool calls to TransactionTools.handleTool() in the server's CallToolRequestSchema handler.
      return await this.tools.purchases.handleTool(name, args);
    }
    if (name.startsWith('transaction_')) {
      return await this.tools.transactions.handleTool(name, args);
  • Helper method IapticAPI.getTransactions() that makes the actual HTTP GET request to /transactions endpoint on the Iaptic API.
    async getTransactions(params?: ListParams & { purchaseId?: string }) {
      const defaultParams = {
        limit: 100,  // Reasonable default limit
        ...params
      };
      const response = await this.client.get('/transactions', { params: defaultParams });
      return response.data;
    }
Behavior4/5

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

Despite no annotations, description discloses pagination, default limit, ordering (newest first), filtering options, and result contents. Adequately transparent for a list endpoint.

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?

Concise, well-structured with bullet points and front-loaded purpose. Each sentence adds useful information without excess.

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?

Covers purpose, pagination, filtering, ordering, result contents, and an important usage tip. No output schema, but description gives sufficient detail for a listing tool.

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%, but description adds value by confirming default limit per page and reinforcing ISO format. Provides slightly more context than 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?

Clearly states 'List financial transactions from your Iaptic account' with a specific verb and resource. However, does not explicitly differentiate from sibling tools like customer_transactions or transaction_get.

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?

Provides guidance on pagination, date filtering, and an important note to avoid retrieving too many records. Lacks explicit when-to-use vs. alternatives (e.g., use transaction_get for a single transaction).

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/iaptic/mcp-server-iaptic'

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