Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

create_address

Add a billing address to a customer's Paddle account, enabling them to complete purchases and meet tax and compliance requirements.

Instructions

This tool will create a new address for a customer in Paddle.

Address entities hold billing address information for a customer. Customers must have an address to make a purchase. A transaction can be created without an address, but it can't go past a status of draft until an address is added.

To make buying as frictionless as possible, Paddle only requires a country. For tax calculation, fraud prevention, and compliance purposes, postalCode is required when creating addresses for some countries, like ZIP codes in the USA and postcodes in the UK.

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 address entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesPaddle ID of the customer.
descriptionNoMemorable description for this address.
firstLineNoFirst line of this address.
secondLineNoSecond line of this address.
cityNoCity of this address.
postalCodeNoZIP or postal code of this address. Required for some countries.
regionNoState, county, or region of this address.
countryCodeYesTwo-letter ISO 3166-1 alpha-2 country code.
customDataNoAny structured custom key-value data needed outside of Paddle's standard fields. Occasionally used by third-parties.

Implementation Reference

  • The core handler function that executes the create_address tool logic by destructuring customerId and address data from params and calling paddle.addresses.create.
    export const createAddress = async (paddle: Paddle, params: z.infer<typeof Parameters.createAddressParameters>) => {
      try {
        const { customerId, ...updateData } = params;
        const address = await paddle.addresses.create(customerId, updateData);
        return address;
      } catch (error) {
        return error;
      }
    };
  • Tool definition including the method name, description, parameters schema reference (params.createAddressParameters), and required actions for the create_address tool.
    {
      method: "create_address",
      name: "Create an address for a customer",
      description: prompts.createAddressPrompt,
      parameters: params.createAddressParameters,
      actions: {
        addresses: {
          write: true,
          create: true,
        },
      },
  • src/api.ts:34-34 (registration)
    Registers the createAddress handler function under the TOOL_METHODS.CREATE_ADDRESS key in the toolMap for tool invocation.
    [TOOL_METHODS.CREATE_ADDRESS]: funcs.createAddress,
  • Defines the string constant for the create_address tool method name.
    CREATE_ADDRESS: "create_address",
Behavior4/5

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

Annotations indicate this is a mutation tool (readOnlyHint: false), and the description correctly describes it as a creation operation. It adds valuable behavioral context beyond annotations by explaining the business impact (addresses needed for purchases), requirements (country mandatory, postalCode sometimes required), and what happens on success (response includes new address entity). No contradiction with annotations exists.

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 appropriately front-loaded with purpose and context, but includes generic agent guidance ('Ensure you have all the information...', 'Don't fabricate...') that doesn't add tool-specific value. These sentences could be removed without losing essential tool understanding, making the description somewhat verbose for its core purpose.

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?

For a mutation tool with no output schema, the description provides good context about what the tool does, when to use it, requirements, and success behavior. It covers the essential aspects given the annotations (which indicate it's non-destructive) and parameter coverage. The main gap is lack of explicit error handling or rate limit information, but overall it's fairly complete.

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 schema already documents all 9 parameters thoroughly. The description adds some semantic context about country and postalCode requirements (e.g., 'postalCode is required when creating addresses for some countries'), but doesn't provide significant additional meaning beyond what's in the schema descriptions. 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 with specific verb ('create') and resource ('address for a customer in Paddle'), and distinguishes it from siblings by explaining that addresses are needed for purchases and transactions. It provides context about address entities holding billing information, which differentiates it from other 'create_' tools like create_customer or create_transaction.

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

Usage Guidelines4/5

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

The description provides clear context about when addresses are needed ('Customers must have an address to make a purchase', 'transaction can't go past draft until an address is added'), and mentions country requirements for tax/fraud purposes. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the sibling tools, such as when to use get_address or list_addresses instead.

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