Skip to main content
Glama
PaddleHQ
by PaddleHQ

get_notification

Retrieve a Paddle notification by its ID to check delivery status, debug issues, and view event details for up to 90 days.

Instructions

This tool will retrieve a notification from Paddle by its ID.

When an event that has a notification destination occurs, Paddle creates a notification entity with information about the notification.

Notifications older than 90 days aren't retained. If trying to get a notification that's no longer retained, Paddle returns an error.

Check the following details to understand the success or failure of the notification according to Paddle and debug issues:

  • status: Status of the notification.

    • notAttempted: Paddle hasn't yet tried to deliver this notification.

    • needsRetry: Paddle tried to deliver this notification, but it failed. It's scheduled to be retried.

    • delivered: Paddle delivered this notification successfully.

    • failed: Paddle tried to deliver this notification, but all attempts failed. It's not scheduled to be retried.

  • origin: Describes how this notification was created.

    • event: Notification created when a subscribed event occurred.

    • replay: Notification created when a notification with the origin event was replayed.

  • deliveredAt: RFC 3339 datetime string of when this notification was delivered. null if not yet delivered successfully.

  • lastAttemptAt: RFC 3339 datetime string of when this notification was last attempted.

  • retryAt: RFC 3339 datetime string of when this notification is scheduled to be retried.

  • timesAttempted: How many times delivery of this notification has been attempted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notificationIdYesPaddle ID of the notification.

Implementation Reference

  • The handler function that executes the get_notification tool. It takes a notificationId parameter and retrieves the notification using the Paddle SDK's notifications.get method.
    export const getNotification = async (paddle: Paddle, params: z.infer<typeof Parameters.getNotificationParameters>) => { try { const { notificationId } = params; const notification = await paddle.notifications.get(notificationId); return notification; } catch (error) { return error; } };
  • The tool schema definition, including method name, description from prompts, input parameters schema, and required actions/permissions.
    method: "get_notification", name: "Get a notification", description: prompts.getNotificationPrompt, parameters: params.getNotificationParameters, actions: { notifications: { read: true, get: true, }, },
  • src/api.ts:52-52 (registration)
    Registration of the tool handler in the API's toolMap, mapping the constant TOOL_METHODS.GET_NOTIFICATION to the getNotification function.
    [TOOL_METHODS.GET_NOTIFICATION]: funcs.getNotification,
  • src/constants.ts:44-44 (registration)
    Constant definition for the tool method string 'get_notification'.
    GET_NOTIFICATION: "get_notification",

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