Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_notification_settings

Read-only

Retrieve and manage notification settings in Paddle Billing, with options to filter by active status, traffic source, and paginate results for comprehensive configuration review.

Instructions

This tool will list notification settings in Paddle.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter notification settings by active and trafficSource 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.

The endpointSecretKey is returned for webhook signature verification, but is a secure value and should never be shared, never be made publicly-accessible, and should only be stored securely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
perPageNoSet how many entities are returned per page. Returns the maximum number of results if a number greater than the maximum is requested.
orderByNoOrder returned entities by the specified field and direction.
activeNoDetermine whether returned entities are active (`true`) or not (`false`).
trafficSourceNoReturn entities that match the specified traffic source.

Implementation Reference

  • The handler function that executes the tool logic by calling paddle.notificationSettings.list(params) and handling errors.
    export const listNotificationSettings = async (
      paddle: Paddle,
      params: z.infer<typeof Parameters.listNotificationSettingsParameters>,
    ) => {
      try {
        const result = await paddle.notificationSettings.list(params);
        return result;
      } catch (error) {
        return error;
      }
    };
  • Tool schema definition including method name, description, parameters schema reference, and required actions.
      method: "list_notification_settings",
      name: "List notification settings",
      description: prompts.listNotificationSettingsPrompt,
      parameters: params.listNotificationSettingsParameters,
      actions: {
        notificationSettings: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:45-45 (registration)
    Registration of the tool handler function in the toolMap for execution.
    [TOOL_METHODS.LIST_NOTIFICATION_SETTINGS]: funcs.listNotificationSettings,
  • Constant defining the tool method string identifier.
    LIST_NOTIFICATION_SETTINGS: "list_notification_settings",
Behavior4/5

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

Annotations provide readOnlyHint=true, but the description adds valuable behavioral context beyond that: it explains pagination mechanics ('use the after parameter with the last ID'), recommends a default perPage value (200), warns about secure handling of endpointSecretKey, and mentions sorting capabilities. This significantly enhances understanding of how the tool behaves in practice.

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 (6 sentences) and front-loaded with the core purpose. Each sentence adds value: default behavior, filtering guidance, pagination mechanics, sorting, and security warning. There's minimal redundancy, though the security warning about endpointSecretKey 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 no output schema, the description provides good completeness: it covers purpose, pagination behavior, filtering parameters, sorting, and security considerations. The main gap is lack of output format details (what fields are returned beyond endpointSecretKey), but given it's a list operation with good parameter coverage, this is acceptable.

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 semantic context: it explains that perPage defaults to 200 maximum, that active and trafficSource are filters 'as needed', and that after uses 'the last ID from previous results'. However, it doesn't provide significant additional meaning beyond what's already well-documented 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 notification settings in Paddle.' This is a specific verb+resource combination that distinguishes it from other list tools (like list_notifications, list_notification_logs). However, it doesn't explicitly differentiate from get_notification_setting (singular vs. plural), which would require a 5.

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 through parameter explanations (e.g., 'Filter notification settings by active and trafficSource as needed'), but doesn't explicitly state when to use this tool versus alternatives like get_notification_setting or list_notifications. It mentions pagination behavior but lacks explicit 'when-not' scenarios or sibling tool comparisons.

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