Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_prices

Read-only

Retrieve and filter catalog prices from your Paddle account with pagination, sorting, and options to include related product details.

Instructions

This tool will list prices in the account's catalog.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter prices by id, productId, status, recurring, and type 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. Amounts are in the smallest currency unit (e.g., cents).

Use the include parameter to include related entities in the response:

  • product: An object for the product entity that's tied to the price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
includeNoInclude related entities in the response.
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.
productIdNoReturn entities related to the specified product. Use a comma-separated list to specify multiple product IDs.
statusNoReturn entities that match the specified status. Use a comma-separated list to specify multiple status values.
recurringNoDetermine whether returned entities are for recurring prices (`true`) or one-time prices (`false`).
typeNoReturn items that match the specified type.

Implementation Reference

  • The core handler function for the "list_prices" tool. It invokes paddle.prices.list(params), fetches the first page of results with next(), extracts pagination metadata using the paginationData helper, and returns an object containing pagination info and the list of prices.
    export const listPrices = async (paddle: Paddle, params: z.infer<typeof Parameters.listPricesParameters>) => {
      try {
        const collection = paddle.prices.list(params);
        const prices = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, prices };
      } catch (error) {
        return error;
      }
    };
  • src/tools.ts:70-81 (registration)
    Tool registration in the tools array exported from tools.ts. Defines the method name, human-readable name, description prompt, Zod parameters schema reference, and required permissions/actions for the list_prices tool.
    {
      method: "list_prices",
      name: "List prices",
      description: prompts.listPricesPrompt,
      parameters: params.listPricesParameters,
      actions: {
        prices: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:14-14 (registration)
    Maps the TOOL_METHODS.LIST_PRICES constant to the listPrices handler function in the toolMap object, which is used by PaddleAPI.run() to dispatch tool calls to the appropriate handler.
    [TOOL_METHODS.LIST_PRICES]: funcs.listPrices,
  • Helper utility function used by the listPrices handler (and other list handlers) to extract pagination metadata (hasMore, estimatedTotal) from Paddle SDK collection objects.
    const paginationData = (collection: PaginatedCollection) => ({
      hasMore: collection.hasMore,
      estimatedTotal: collection.estimatedTotal,
    });
  • src/constants.ts:6-6 (registration)
    Constant definition for the "list_prices" tool method string, used as keys in registrations in api.ts and tools.ts.
    LIST_PRICES: "list_prices",
Behavior4/5

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

Annotations provide readOnlyHint=true, indicating it's a safe read operation. The description adds valuable behavioral context beyond this: it explains pagination behavior ('Results are paginated'), currency units ('Amounts are in the smallest currency unit'), and includes details on the 'include' parameter for related entities. This enhances understanding without contradicting annotations.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose. It uses bullet points effectively for the 'include' parameter details, but some sentences could be more concise (e.g., the pagination explanation is slightly verbose). Overall, it's efficient with minimal waste.

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 (9 parameters, pagination, filtering) and the absence of an output schema, the description does a good job covering key aspects: purpose, pagination, filtering options, currency units, and related entities. However, it could improve by mentioning response format or error handling to be fully complete for a list tool.

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 9 parameters thoroughly. The description adds some semantic context, such as recommending a default for 'perPage' and explaining how 'after' works with pagination, but doesn't provide significant additional meaning beyond what the schema specifies. 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's purpose: 'list prices in the account's catalog.' It specifies the verb ('list') and resource ('prices'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_price' (singular) or 'preview_prices,' which might be used for different scenarios.

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 implied usage guidance, such as recommending to 'use the maximum perPage by default (200) to ensure comprehensive results' and explaining when to use the 'after' parameter for pagination. However, it lacks explicit when-to-use vs. alternatives (e.g., compared to 'get_price' for a single price or 'preview_prices' for estimates), and doesn't mention prerequisites or exclusions.

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