Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

get_customer

Read-only

Retrieve customer details from Paddle Billing using their unique customer ID to access account information and manage billing data.

Instructions

This tool will retrieve a customer from Paddle by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesPaddle ID of the customer.

Implementation Reference

  • The main handler function for the 'get_customer' tool. It takes a Paddle SDK instance and parameters, extracts the customerId, calls paddle.customers.get(customerId), and returns the customer or error.
    export const getCustomer = async (paddle: Paddle, params: z.infer<typeof Parameters.getCustomerParameters>) => {
      try {
        const { customerId } = params;
        const customer = await paddle.customers.get(customerId);
        return customer;
      } catch (error) {
        return error;
      }
    };
  • The tool definition object in the tools array, specifying the method name 'get_customer', human-readable name, description prompt, Zod parameters schema reference, and required permissions/actions for customers (read/get).
      method: "get_customer",
      name: "Get a customer",
      description: prompts.getCustomerPrompt,
      parameters: params.getCustomerParameters,
      actions: {
        customers: {
          read: true,
          get: true,
        },
      },
    },
  • src/api.ts:31-31 (registration)
    Registration of the getCustomer handler function in the toolMap object, mapping the GET_CUSTOMER constant to the function for execution in PaddleAPI.run().
    [TOOL_METHODS.GET_CUSTOMER]: funcs.getCustomer,
  • src/constants.ts:23-23 (registration)
    Constant definition for the tool method key 'GET_CUSTOMER' mapping to the string 'get_customer', used in tool definitions and mappings.
    GET_CUSTOMER: "get_customer",
Behavior3/5

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

The description doesn't add behavioral context beyond what annotations provide. Annotations declare readOnlyHint=true, which already indicates this is a safe read operation. The description doesn't disclose additional traits like authentication requirements, rate limits, error conditions, or what happens if the customer ID doesn't exist.

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 extremely concise - a single sentence that directly states the tool's purpose with zero wasted words. It's perfectly front-loaded and appropriately sized for this simple retrieval tool.

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?

For a simple read operation with good annotations (readOnlyHint) and full parameter documentation, the description is minimally adequate. However, without an output schema and with no behavioral context about what gets returned or error conditions, there are clear gaps in completeness for agent usage.

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 already fully documents the single 'customerId' parameter. The description doesn't add any meaningful semantic context beyond what's in the schema - it mentions retrieving by ID but doesn't explain format, validation, or examples.

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 ('retrieve') and resource ('a customer from Paddle'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_customers' or 'get_customer' vs other 'get_' tools, which would be needed for a perfect score.

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. There's no mention of prerequisites, when to choose this over 'list_customers', or any context about its specific use case compared to other customer-related tools in the sibling list.

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