Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_businesses

Read-only

Retrieve and filter businesses for a specific Paddle customer, with options for pagination, search by name or tax details, and status filtering.

Instructions

This tool will list businesses for a customer in Paddle.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter businesses by id, search (fuzzy search on the business's name or tax or VAT number), 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 business's name or tax or VAT number.
statusNoReturn entities that match the specified status. Use a comma-separated list to specify multiple status values.

Implementation Reference

  • The handler function for the 'list_businesses' tool. It lists businesses associated with a customer using the Paddle SDK's businesses.list method, handles the first page of results, extracts pagination data, and returns the businesses with pagination info. Catches and returns any errors.
    export const listBusinesses = async (paddle: Paddle, params: z.infer<typeof Parameters.listBusinessesParameters>) => {
      try {
        const { customerId, ...queryParams } = params;
        const collection = paddle.businesses.list(customerId, queryParams);
        const businesses = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, businesses };
      } catch (error) {
        return error;
      }
    };
  • Tool schema definition including method name, description from prompts, Zod parameters schema reference (params.listBusinessesParameters), and required actions (read/list on businesses). This configures the tool for MCP usage.
      method: "list_businesses",
      name: "List businesses for a customer",
      description: prompts.listBusinessesPrompt,
      parameters: params.listBusinessesParameters,
      actions: {
        businesses: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:37-37 (registration)
    Registers the 'list_businesses' tool by mapping the constant TOOL_METHODS.LIST_BUSINESSES to the handler function funcs.listBusinesses in the toolMap used by PaddleAPI.run().
    [TOOL_METHODS.LIST_BUSINESSES]: funcs.listBusinesses,
  • src/constants.ts:29-29 (registration)
    Defines the constant TOOL_METHODS.LIST_BUSINESSES = 'list_businesses' used for tool identification in registrations and mappings.
    LIST_BUSINESSES: "list_businesses",
  • Helper function to extract pagination metadata (hasMore, estimatedTotal) from Paddle's PaginatedCollection, used by the list_businesses handler and other list functions.
    const paginationData = (collection: PaginatedCollection) => ({
      hasMore: collection.hasMore,
      estimatedTotal: collection.estimatedTotal,
    });
Behavior4/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds valuable behavioral context beyond this: it specifies default pagination behavior ('maximum perPage by default (200)'), explains pagination mechanics ('use the 'after' parameter with the last ID'), and details filtering options (id, search, status). This enriches the agent's understanding of how the tool behaves in practice, though it doesn't cover rate limits or auth needs. The description complements annotations well without contradiction.

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 efficiently structured with four sentences, each serving a distinct purpose: stating the tool's purpose, recommending a default, detailing filtering options, and explaining pagination and sorting. There is no wasted text, and information is front-loaded with the core function. This makes it easy for an agent to parse and apply the guidance quickly.

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, filtering) and the presence of annotations (readOnlyHint) but no output schema, the description does a good job of covering key aspects: purpose, usage, and behavioral traits. It explains pagination, filtering, and sorting, which are critical for effective use. However, it doesn't describe the return format or error handling, leaving some gaps. With annotations providing safety context, it's largely complete but not exhaustive.

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%, meaning all parameters are documented in the schema. The description adds some semantic context: it clarifies that 'search' performs 'fuzzy search on the business's name or tax or VAT number' (vs. schema's 'exact match'), and it provides usage tips for 'after' and 'orderBy.' However, it doesn't significantly enhance meaning beyond the schema, such as explaining parameter interactions or edge cases. Baseline 3 is appropriate given 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's purpose: 'list businesses for a customer in Paddle.' It specifies the verb ('list'), resource ('businesses'), and scope ('for a customer'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'list_customers' or 'get_business,' though the scope implies it's for businesses under a specific customer. This clarity earns a 4, as it's clear but lacks explicit sibling differentiation.

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 on when to use this tool: for listing businesses with filtering, pagination, and sorting capabilities. It implicitly suggests usage for comprehensive results by recommending 'maximum perPage by default (200).' However, it doesn't explicitly state when not to use it or name alternatives (e.g., 'get_business' for single businesses), which prevents a perfect score. The guidance is strong but not exhaustive.

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