Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_events

Read-only

Retrieve and manage event records from Paddle Billing to track subscription changes, transactions, and other notable actions for comprehensive monitoring and reporting.

Instructions

This tool will list events in Paddle.

When something notable occurs, Paddle creates an event entity with information about what happened. Events are created for actions regardless of how they happened and regardless of whether a notification setting is subscribed to be notified by Paddle.

Some actions might create multiple events. For example, resuming a subscription typically results in a subscription.resumed, transaction.created, and other transaction events being created.

Use the maximum perPage by default (200) to ensure comprehensive results. 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
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
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.

Implementation Reference

  • The handler function for the 'list_events' tool. It calls paddle.events.list(params), fetches the first page of events, computes pagination data, and returns the results or any error.
    export const listEvents = async (paddle: Paddle, params: z.infer<typeof Parameters.listEventsParameters>) => {
      try {
        const collection = paddle.events.list(params);
        const events = await collection.next();
        const pagination = paginationData(collection);
        return { pagination, events };
      } catch (error) {
        return error;
      }
    };
  • The tool schema definition for 'list_events', including method name, description from prompts, input parameters schema reference, and required actions/permissions.
      method: "list_events",
      name: "List events",
      description: prompts.listEventsPrompt,
      parameters: params.listEventsParameters,
      actions: {
        events: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:50-50 (registration)
    Registration of the listEvents handler function in the toolMap used by PaddleAPI to dispatch tool calls.
    [TOOL_METHODS.LIST_EVENTS]: funcs.listEvents,
  • src/constants.ts:42-42 (registration)
    Constant definition for the LIST_EVENTS tool method string, used in registration and tool definitions.
    LIST_EVENTS: "list_events",
  • Helper function to extract pagination metadata from Paddle collection objects, used in listEvents and other list handlers.
    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?

The description adds valuable behavioral context beyond the readOnlyHint annotation: it explains that events are created for all notable actions regardless of notification settings, that some actions create multiple events, and provides specific pagination guidance (maximum 200 per page, use 'after' for next page). This goes well beyond what the annotation alone provides about read-only access.

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 appropriately sized. It starts with the core purpose, provides context about events, gives important behavioral details, and ends with specific usage instructions. Each sentence adds value, though the middle paragraph about event creation could be slightly more concise.

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 list tool with readOnlyHint annotation and good schema coverage, the description provides comprehensive context. It explains what events are, how they're created, pagination behavior, and usage patterns. The main gap is lack of output format details (no output schema exists), but otherwise it's quite complete for this type of 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?

With 100% schema description coverage, the baseline is 3. The description adds some value by explaining practical usage of parameters (use 'after' with last ID for pagination, use orderBy for sorting, perPage maximum is 200), but doesn't provide additional semantic meaning beyond what's already in the schema descriptions.

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 events in Paddle' with additional context about what events are ('notable occurrences' with entity creation). It distinguishes from siblings by focusing specifically on events rather than other resources like addresses, customers, or transactions. However, it doesn't explicitly differentiate from other list_* tools beyond the resource type.

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 usage guidance for pagination ('use the after parameter'), sorting ('use the orderBy parameter'), and default behavior ('use maximum perPage by default'). It explains when to use pagination parameters but doesn't explicitly state when to choose this tool over alternatives or mention any prerequisites for using it.

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