list_notification_logs
Retrieve delivery attempt logs for Paddle notifications to monitor webhook responses, debug failures, and track delivery status.
Instructions
This tool will list notification logs in Paddle.
When Paddle sends a notification to a webhook endpoint or email address, it records information about each delivery attempt as a log against the notification.
Every delivered notification has at least one log with information about the response that Paddle received on delivery.
Where a notification isn't delivered successfully, Paddle tries to deliver the notification again. Each delivery attempt is logged against a notification.
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.
Check the following details to understand the success or failure of each delivery attempt and debug issues:
responseCode: HTTP code sent by the responding server.
responseContentType: Content-Type sent by the responding server.
responseBody: Response body sent by the responding server. Typically empty for success responses.
attemptedAt: RFC 3339 datetime string of when Paddle attempted to deliver the related notification.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notificationId | Yes | Paddle ID of the notification. | |
| after | Yes | Return entities after the specified Paddle ID when working with paginated endpoints. | |
| perPage | Yes | Set how many entities are returned per page. Returns the maximum number of results if a number greater than the maximum is requested. |
Implementation Reference
- src/functions.ts:536-549 (handler)The main handler function implementing the list_notification_logs tool. It takes Paddle instance and parameters, fetches notification logs with pagination using paddle.notifications.getLogs, and returns paginated notifications or error.
export const listNotificationLogs = async ( paddle: Paddle, params: z.infer<typeof Parameters.listNotificationLogsParameters>, ) => { try { const { notificationId, ...queryParams } = params; const collection = paddle.notifications.getLogs(notificationId, queryParams); const notifications = await collection.next(); const pagination = paginationData(collection); return { pagination, notifications }; } catch (error) { return error; } }; - src/tools.ts:782-792 (schema)The MCP tool schema definition for list_notification_logs, including method name, description prompt reference, input parameters schema reference, and required permission actions.
method: "list_notification_logs", name: "List logs for a notification", description: prompts.listNotificationLogsPrompt, parameters: params.listNotificationLogsParameters, actions: { notificationLogs: { read: true, list: true, }, }, }, - src/api.ts:53-53 (registration)Registration of the listNotificationLogs handler function in the toolMap under the LIST_NOTIFICATION_LOGS key for runtime execution.
[TOOL_METHODS.LIST_NOTIFICATION_LOGS]: funcs.listNotificationLogs, - src/constants.ts:45-45 (helper)Constant definition for the tool method name string used across the codebase for registration and mapping.
LIST_NOTIFICATION_LOGS: "list_notification_logs",