Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

create_customer

Create new customer records in Paddle Billing to store purchaser information for transactions, invoices, and business associations.

Instructions

This tool will create a new customer in Paddle.

Customer entities hold information about the people and businesses that make purchases.

Customers have two sub-entities:

  • addresses: Customers require an address to make a purchase, which can be created through the create_address tool. Can have multiple addresses.

  • businesses: Customers can optionally be associated with businesses, which can be created through the create_business tool.

Ensure you have all the information needed before making the call. Don't fabricate, imagine, or infer details and parameter values unless explicitly asked to. If anything is ambiguous, unknown, or unclear, ask the user for clarification or details before you proceed.

If successful, the response includes a copy of the new customer entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFull name of this customer. Required when creating transactions where `collectionMode` is `manual` (invoices).
emailYesEmail address for this customer.
customDataNoAny structured custom key-value data needed outside of Paddle's standard fields. Occasionally used by third-parties.
localeNoValid IETF BCP 47 short form locale tag. If omitted, defaults to `en`.

Implementation Reference

  • The main handler function for the 'create_customer' tool. It uses the Paddle SDK to create a new customer with the provided parameters.
    export const createCustomer = async (paddle: Paddle, params: z.infer<typeof Parameters.createCustomerParameters>) => {
      try {
        const customer = await paddle.customers.create(params);
        return customer;
      } catch (error) {
        return error;
      }
    };
  • The tool schema definition in the tools array, specifying the method name, description, parameters schema (Zod), and required actions for 'create_customer'.
      method: "create_customer",
      name: "Create a customer",
      description: prompts.createCustomerPrompt,
      parameters: params.createCustomerParameters,
      actions: {
        customers: {
          write: true,
          create: true,
        },
      },
    },
  • src/api.ts:30-30 (registration)
    Registration of the 'create_customer' tool in the toolMap, mapping TOOL_METHODS.CREATE_CUSTOMER to the createCustomer handler function.
    [TOOL_METHODS.CREATE_CUSTOMER]: funcs.createCustomer,
  • src/constants.ts:22-22 (registration)
    Constant definition for the tool method name 'create_customer' used in registration and tool definitions.
    CREATE_CUSTOMER: "create_customer",
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which the description doesn't contradict. The description adds context about sub-entities (addresses, businesses) and the response format ('includes a copy of the new customer entity'), which provides useful behavioral information beyond annotations. However, it doesn't cover aspects like rate limits, authentication needs, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes some redundant or overly general advice (e.g., 'Don't fabricate, imagine, or infer details'). The first two paragraphs are well-structured, but the latter part contains generic guidance that could be streamlined. It's front-loaded with purpose but could be more efficient.

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 complexity (creation operation, 4 parameters, no output schema), the description provides basic context about sub-entities and response format. However, it lacks details on error handling, idempotency, or system-specific constraints. With annotations covering safety but no output schema, the description is adequate but not comprehensive.

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%, so the schema already documents all four parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining relationships between parameters or providing examples. 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'create a new customer in Paddle' and explains that 'Customer entities hold information about the people and businesses that make purchases.' This provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'create_business' or 'create_address' beyond mentioning their relationship.

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?

The description provides some usage guidance with 'Ensure you have all the information needed before making the call' and mentions related sub-entities (addresses, businesses) that can be created through sibling tools. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_customer' or 'list_customers,' nor does it provide clear exclusions or prerequisites beyond general caution.

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