Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_subscriptions

Read-only

Retrieve and filter subscription data from Paddle Billing. Use pagination, sorting, and parameters like status, customer ID, or price ID to manage subscription information.

Instructions

This tool will list subscriptions in Paddle.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter subscriptions by addressId, collectionMode, customerId, id, priceId, scheduledChangeAction, 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.

Amounts are in the smallest currency unit (e.g., cents).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressIdNoReturn entities related to the specified address. Use a comma-separated list to specify multiple address IDs.
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
collectionModeNoReturn entities that match the specified collection mode.
customerIdNoReturn entities related to the specified customer. Use a comma-separated list to specify multiple customer IDs.
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.
priceIdNoReturn entities related to the specified price. Use a comma-separated list to specify multiple price IDs.
scheduledChangeActionNoReturn subscriptions that have a scheduled change. Use a comma-separated list to specify multiple scheduled change actions.
statusNoReturn entities that match the specified status. Use a comma-separated list to specify multiple status values.

Implementation Reference

  • The handler function that executes the list_subscriptions tool logic, using the Paddle SDK to list subscriptions with pagination.
    export const listSubscriptions = async (
      paddle: Paddle,
      params: z.infer<typeof Parameters.listSubscriptionsParameters>,
    ) => {
      try {
        const collection = paddle.subscriptions.list(params);
        const subscriptions = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, subscriptions };
      } catch (error) {
        return error;
      }
    };
  • The tool schema definition for list_subscriptions, including name, description, input parameters schema (Zod object), and required actions.
    {
      method: "list_subscriptions",
      name: "List subscriptions",
      description: prompts.listSubscriptionsPrompt,
      parameters: params.listSubscriptionsParameters,
      actions: {
        subscriptions: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:77-77 (registration)
    Registration of the listSubscriptions handler function in the toolMap for the LIST_SUBSCRIPTIONS method.
    [TOOL_METHODS.LIST_SUBSCRIPTIONS]: funcs.listSubscriptions,
  • Constant definition for the LIST_SUBSCRIPTIONS tool method string.
    LIST_SUBSCRIPTIONS: "list_subscriptions",
Behavior4/5

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

Annotations provide readOnlyHint=true, and the description adds valuable behavioral context beyond that: it specifies pagination behavior ('Results are paginated'), recommends a default perPage value ('Use the maximum perPage by default (200)'), and notes currency formatting ('Amounts are in the smallest currency unit'). 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 appropriately sized with 5 sentences, each adding value: purpose, default usage, filtering, pagination, sorting, and currency details. It's front-loaded with the core purpose and key usage tip. Minor redundancy exists in listing filter fields that are already in the schema.

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 (10 parameters, no output schema), the description is fairly complete: it covers purpose, key behavioral traits (pagination, defaults, currency), and usage hints. With annotations covering read-only safety, it doesn't need to explain return values deeply, though output format details could be more explicit.

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 10 parameters thoroughly. The description adds minimal param semantics by listing filterable fields and mentioning pagination with 'after', but doesn't provide significant additional meaning beyond what's in the schema. 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 as 'list subscriptions in Paddle,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_subscription' or other list tools, though the context suggests it's for bulk retrieval with filtering.

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 doesn't explicitly state when to use this tool versus alternatives like 'get_subscription' for single items or other list tools for different resources. No exclusions or clear alternatives are named.

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