Skip to main content
Glama
alamedaim-apps

Authorize.net MCP Server

get_customer_profile_transaction_list

Retrieve all transaction records for a specific customer profile ID from Authorize.net payment history to review payment activity and track customer purchases.

Instructions

Get all transactions for a specific customer profile ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerProfileIdYesThe customer profile ID to retrieve transactions for.

Implementation Reference

  • The main handler function that fetches the transaction list for a given customer profile ID using the Authorize.Net GetTransactionListForCustomer API.
    async function getCustomerProfileTransactionList(customerProfileId: string) {
      const request = new ApiContracts.GetTransactionListForCustomerRequest();
      request.setMerchantAuthentication(getMerchantAuth());
      request.setCustomerProfileId(customerProfileId);
    
      const ctrl = new ApiControllers.GetTransactionListForCustomerController(request.getJSON());
      const response = await executeController(ctrl);
    
      const apiResponse = new ApiContracts.GetTransactionListResponse(response);
      if (apiResponse.getMessages().getResultCode() !== ApiContracts.MessageTypeEnum.OK) {
        const errors = apiResponse.getMessages().getMessage();
        throw new Error(`API Error: ${errors[0].getCode()} - ${errors[0].getText()}`);
      }
    
      return apiResponse.getTransactions() || [];
    }
  • Input schema defining the required 'customerProfileId' parameter as a string.
    inputSchema: {
      type: "object",
      properties: {
        customerProfileId: {
          type: "string",
          description: "The customer profile ID to retrieve transactions for.",
        },
      },
      required: ["customerProfileId"],
    },
  • src/index.ts:239-252 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    {
      name: "get_customer_profile_transaction_list",
      description: "Get all transactions for a specific customer profile ID.",
      inputSchema: {
        type: "object",
        properties: {
          customerProfileId: {
            type: "string",
            description: "The customer profile ID to retrieve transactions for.",
          },
        },
        required: ["customerProfileId"],
      },
    },
  • Dispatcher switch case that routes the tool call to the handler function.
    case "get_customer_profile_transaction_list":
      result = await getCustomerProfileTransactionList(args?.customerProfileId as string);
      break;
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states it 'Get[s] all transactions' but doesn't clarify what 'all' means (e.g., date range limits, pagination, return format, or whether it includes historical/archived data). For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence contributes directly to understanding what the tool does, making it appropriately sized and well-structured.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It lacks behavioral details (e.g., transaction scope, pagination) and differentiation from siblings, which are important for an agent to use it correctly in context with other transaction-related tools.

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%, with the single parameter 'customerProfileId' fully documented in the schema. The description adds no additional meaning beyond implying the parameter identifies the customer, which the schema already states. This meets the baseline score of 3 when schema coverage is high.

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 ('Get') and resource ('transactions') with a specific scope ('for a specific customer profile ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_transaction_list' or 'get_unsettled_transaction_list', which likely serve similar transaction retrieval functions.

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. With siblings like 'get_transaction_list' and 'get_unsettled_transaction_list' present, there's no indication whether this tool is for settled/unsettled transactions, batch filtering, or other distinctions that would help an agent choose correctly.

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/alamedaim-apps/authnet-mcp'

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