Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_addresses

Read-only

Retrieve and manage customer addresses in Paddle with filtering, pagination, and sorting options for efficient address management.

Instructions

This tool will list addresses for a customer in Paddle.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter addresses by id, search (fuzzy search on the address's street, city, state, postalCode, or country), and status 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.
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
idNoReturn only the IDs specified. Use a comma-separated list to get multiple entities.
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.
searchNoReturn entities that match a search query. Pass an exact match for the street, city, state, postal code, or country.
statusNoReturn entities that match the specified status. Use a comma-separated list to specify multiple status values.

Implementation Reference

  • The main handler function that executes the list_addresses tool. It takes a customerId and optional query parameters, lists addresses using the Paddle SDK, fetches the first page, adds pagination info, and returns the result or error.
    export const listAddresses = async (paddle: Paddle, params: z.infer<typeof Parameters.listAddressesParameters>) => {
      try {
        const { customerId, ...queryParams } = params;
        const collection = paddle.addresses.list(customerId, queryParams);
        const addresses = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, addresses };
      } catch (error) {
        return error;
      }
    };
  • src/tools.ts:277-287 (registration)
    MCP tool registration block defining the list_addresses tool, including method name, human name, description prompt reference, Zod parameters schema reference, and required actions (read/list on addresses).
      method: "list_addresses",
      name: "List addresses for a customer",
      description: prompts.listAddressesPrompt,
      parameters: params.listAddressesParameters,
      actions: {
        addresses: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:33-33 (registration)
    Maps the LIST_ADDRESSES tool method constant to the listAddresses handler function in the PaddleAPI toolMap for execution.
    [TOOL_METHODS.LIST_ADDRESSES]: funcs.listAddresses,
  • Helper function to extract pagination metadata (hasMore, estimatedTotal) from Paddle SDK collection objects, used in the listAddresses handler.
    const paginationData = (collection: PaginatedCollection) => ({
      hasMore: collection.hasMore,
      estimatedTotal: collection.estimatedTotal,
    });
  • Constant defining the string identifier for the list_addresses tool method, used in registrations and mappings.
    LIST_ADDRESSES: "list_addresses",
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description aligns with this by describing a listing operation without contradictions. It adds valuable behavioral context beyond annotations, such as recommending a default perPage value (200), explaining pagination mechanics with 'after' parameter, and noting that results are paginated—details not covered by annotations alone.

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 well-structured and concise, with four sentences that each serve a clear purpose: stating the tool's purpose, recommending a default, explaining filtering, and detailing pagination and sorting. No wasted words, and it's front-loaded with essential information.

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 complexity (7 parameters, pagination) and lack of output schema, the description does a good job covering key aspects like default usage, filtering, and pagination. However, it doesn't detail the response format or error handling, which could be helpful for an agent. With annotations providing safety info, it's mostly complete but has minor gaps.

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 parameters thoroughly. The description adds some semantic context by explaining how to use 'after' for pagination and 'search' for fuzzy matching, but this mostly reinforces rather than extends the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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's purpose as 'list addresses for a customer in Paddle,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_address' (singular) or other list tools, though the context of listing addresses for a specific customer is reasonably distinct.

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 implied usage guidance by mentioning filtering, pagination, and sorting, but it doesn't explicitly state when to use this tool versus alternatives like 'get_address' or other list tools. No clear exclusions or prerequisites are mentioned, leaving some ambiguity for the agent.

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