Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_saved_payment_methods

Read-only

Retrieve saved payment methods for a customer to present at checkout, filtering by address and checkout support with paginated results.

Instructions

This tool will list payment methods for a customer in Paddle.

These are payment methods saved by the customer at checkout to be presented for future purchases. They aren't payment methods stored for transactions related to a recurring subscription. View a customers most recently used payment method for purchases or subscriptions by listing transactions (with the list_transactions tool) with a filter of customerId or subscriptionId, and looking at the returned payments[].methodDetails object.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter payment methods by addressId and supportsCheckout as needed. Results are paginated - use the 'after' parameter with the last ID from previous results to get the next page. Sort and order results using the orderBy parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesPaddle ID of the customer.
addressIdNoReturn entities related to the specified address. Use a comma-separated list to specify multiple address IDs.
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
orderByNoOrder returned entities by the specified field and direction.
perPageNoSet how many entities are returned per page. Returns the maximum number of results if a number greater than the maximum is requested.
supportsCheckoutNoReturn entities that support being presented at checkout (`true`) or not (`false`).

Implementation Reference

  • The core handler function implementing the logic to list saved payment methods for a given customer using the Paddle SDK. It handles pagination and errors.
    export const listSavedPaymentMethods = async (
      paddle: Paddle,
      params: z.infer<typeof Parameters.listSavedPaymentMethodsParameters>,
    ) => {
      try {
        const { customerId, ...queryParams } = params;
        const collection = paddle.paymentMethods.list(customerId, queryParams);
        const paymentMethods = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, paymentMethods };
      } catch (error) {
        return error;
      }
    };
  • Tool configuration including the Zod input schema reference, description prompt, and required permissions/actions for listing saved payment methods.
      method: "list_saved_payment_methods",
      name: "List payment methods saved for a customer",
      description: prompts.listSavedPaymentMethodsPrompt,
      parameters: params.listSavedPaymentMethodsParameters,
      actions: {
        savedPaymentMethods: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:41-41 (registration)
    Maps the tool method constant to its handler function in the PaddleAPI toolMap for execution.
    [TOOL_METHODS.LIST_SAVED_PAYMENT_METHODS]: funcs.listSavedPaymentMethods,
  • src/constants.ts:33-33 (registration)
    Defines the string constant for the tool method name used across the codebase.
    LIST_SAVED_PAYMENT_METHODS: "list_saved_payment_methods",
  • Helper function used by the handler to extract pagination metadata from the Paddle collection.
    const paginationData = (collection: PaginatedCollection) => ({
      hasMore: collection.hasMore,
      estimatedTotal: collection.estimatedTotal,
    });
Behavior4/5

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

The description adds valuable behavioral context beyond the readOnlyHint annotation. It explains that results are paginated with instructions on using the 'after' parameter, recommends a default perPage value for comprehensiveness, and clarifies the nature of the data (saved payment methods for checkout vs. subscriptions). No contradictions with annotations exist.

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?

The description is well-structured and front-loaded with the core purpose, followed by usage notes and parameter guidance. Each sentence adds value, such as distinguishing from sibling tools and explaining pagination. It could be slightly more concise by integrating some details, but overall it avoids redundancy and is efficiently organized.

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 lack of an output schema and the tool's complexity (6 parameters, pagination), the description provides sufficient context for effective use. It covers key behavioral aspects like pagination, filtering, and sibling tool differentiation. However, it does not detail the structure of returned payment methods, which could be helpful since there's no output schema.

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?

With 100% schema description coverage, the input schema fully documents all parameters. The description adds minimal semantic context, such as implying that 'addressId' and 'supportsCheckout' are optional filters, but does not provide significant additional meaning beyond what the schema already specifies. This 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.

Purpose5/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 payment methods for a customer in Paddle' with the specific resource 'saved payment methods at checkout.' It distinguishes from sibling tools by explicitly contrasting with 'list_transactions' for subscription-related payment methods, making the scope unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: it specifies that this tool is for saved payment methods at checkout, not for subscription transactions, and directs users to 'list_transactions' for the latter. It also advises on default usage ('Use the maximum perPage by default') and when to apply filters.

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

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