Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

get_saved_payment_method

Read-only

Retrieve a customer's saved payment method from Paddle using customer and payment method IDs to access stored checkout details for future purchases.

Instructions

This tool will retrieve a payment method for a customer from Paddle using its ID and related customer ID.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesPaddle ID of the customer.
paymentMethodIdYesPaddle ID of the payment method.

Implementation Reference

  • The core handler function that executes the tool logic: retrieves a specific saved payment method for a customer using the Paddle SDK's paymentMethods.get method.
    export const getSavedPaymentMethod = async (
      paddle: Paddle,
      params: z.infer<typeof Parameters.getSavedPaymentMethodParameters>,
    ) => {
      try {
        const { customerId, paymentMethodId } = params;
        const paymentMethod = await paddle.paymentMethods.get(customerId, paymentMethodId);
        return paymentMethod;
      } catch (error) {
        return error;
      }
    };
  • Tool schema definition including the method name, description, Zod parameters schema reference, and required actions for the get_saved_payment_method tool.
      method: "get_saved_payment_method",
      name: "Get a payment method saved for a customer",
      description: prompts.getSavedPaymentMethodPrompt,
      parameters: params.getSavedPaymentMethodParameters,
      actions: {
        savedPaymentMethods: {
          read: true,
          get: true,
        },
      },
    },
  • src/api.ts:41-43 (registration)
    Registration of the getSavedPaymentMethod handler in the toolMap object, mapping the tool method constant to its implementation.
    [TOOL_METHODS.LIST_SAVED_PAYMENT_METHODS]: funcs.listSavedPaymentMethods,
    [TOOL_METHODS.GET_SAVED_PAYMENT_METHOD]: funcs.getSavedPaymentMethod,
    [TOOL_METHODS.DELETE_SAVED_PAYMENT_METHOD]: funcs.deleteSavedPaymentMethod,
  • Constant definition for the tool method name used across registration and tool definitions.
    LIST_SAVED_PAYMENT_METHODS: "list_saved_payment_methods",
    GET_SAVED_PAYMENT_METHOD: "get_saved_payment_method",
    DELETE_SAVED_PAYMENT_METHOD: "delete_saved_payment_method",
Behavior3/5

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

Annotations declare readOnlyHint=true, which the description aligns with by using 'retrieve' (implying a read operation). The description adds valuable context beyond annotations: it clarifies what type of payment methods are retrieved (saved at checkout, not for subscriptions) and provides guidance on alternative approaches for subscription-related payment methods. However, it doesn't mention potential errors, rate limits, or authentication requirements.

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 appropriately sized. The first sentence clearly states the purpose, followed by explanatory context about what these payment methods are and aren't, and ends with guidance on alternatives. Every sentence adds value, though the second sentence could be slightly more concise.

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 moderate complexity (retrieving a specific resource), 100% schema coverage, and readOnlyHint annotation, the description is largely complete. It clarifies the tool's scope and provides usage guidance. The main gap is the lack of output schema, but the description compensates somewhat by explaining what type of data is retrieved.

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 both parameters (customerId and paymentMethodId) clearly documented in the schema. The description adds minimal semantic context beyond the schema, only implying these IDs are Paddle-specific. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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: 'retrieve a payment method for a customer from Paddle using its ID and related customer ID.' It specifies the verb ('retrieve'), resource ('payment method'), and distinguishes it from sibling tools like 'list_saved_payment_methods' (which lists multiple) and 'list_transactions' (which shows recently used methods).

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 vs. alternatives. It states these are 'payment methods saved by the customer at checkout to be presented for future purchases' and clarifies they 'aren't payment methods stored for transactions related to a recurring subscription.' It also explicitly names an alternative tool ('list_transactions') for viewing recently used payment methods.

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