Skip to main content
Glama
pushpad

Pushpad MCP

Official
by pushpad

notifications_get

Retrieve a specific web push notification and its statistics by providing its ID. Only notifications created in the last 35 days are accessible.

Instructions

To get a notification and its stats, send a GET request to /notifications/NOTIFICATION_ID.

Only the notifications created in the last 35 days are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notification_idYesThe ID of a notification.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoA unique identifier for each notification. This is automatically generated upon notification creation.
ttlNoThe number of seconds after which the notification should be dropped if the device of the user is offline.
bodyNoThe main text of the push notification.
tagsNoThe segments that should receive this push notification (i.e. the browsers that have at least one of these tags associated will receive the notification). If both uids and tags are present, only the browsers that match both the conditions will receive the notification (i.e. a browser must be associated to a user ID listed in uids and have at least one of those tags). Instead of simple tags, you can pass boolean expressions that use the operators !, &&, || (from highest to lowest precedence) and can include parentheses. If you pass an array of tags and boolean expressions they are interpreted as ||: the example above is equivalent to "tag0 || tag1 || tagA && !tagB". When the field is omitted or null, it is ignored and the push notification is sent to everyone or to the people specified by uids. When the field is an empty array, the notification will not be sent to anyone.
uidsNoThe users that should receive this push notification. When the field is omitted or null, it is ignored and the push notification is sent to everyone or to the people specified by tags. When the field is an empty array, the notification will not be sent to anyone.
titleNoThe title of the push notification.
silentNoSet to true if you want to disable the notification sound and vibration.
urgentNoSet to true for time-sensitive alerts (e.g. incoming phone call) that must wake up devices that are sleeping.
actionsNoAdd some action buttons to the notification.
send_atNoA time when the notification will be sent.
starredNoBookmark the notification to make it easier to find it from the Pushpad dashboard. You can use this feature to highlight some notifications, for example those that have been sent manually.
icon_urlNoThe url of an image that will be used as the notification icon. Suggested size: 192x192px.
badge_urlNoThe url of a small image (that represents the app or the notification category) that will be displayed when there is not enough space to display the full notification (e.g. Android status bar). Suggested size: 96x96px.
cancelledNoThe notification has been cancelled. A notification can be cancelled on purpose or it can be cancelled by the system (for example if you exceed the usage quota).
image_urlNoThe url of an image that will be displayed in the notification content. Suggested size: 800px for the longer side.
scheduledNoThe deliveries have not started yet. You can try to cancel a notification that is in this status.
created_atNoA time value given in ISO 8601 format. It represents when the notification was created.
project_idNoThe ID of the project the notification belongs to.
target_urlNoThe url the user is redirected to when clicks the push notification.
custom_dataNoAn arbitrary string that represents some metadata that you want to attach to the notification. This string is passed as an argument to the JavaScript functions binded to the action buttons.
opened_countNoThe number of notifications that were clicked or opened.
custom_metricsNoAggregate the stats for this notification into the specified buckets (you can add up to 3 buckets for a single notification). Custom metrics are a way to aggregate the stats for all the notifications that belong to a given category. You need to explicitly create the categories from the project settings before using this feature. You can learn more in the Monitoring section of the documentation.
scheduled_countNoThe number of deliveries that are still in the sending queue.
require_interactionNoSet to true in order to prevent browser from automatically closing the notification after a few seconds. Currently this applies only to Chrome on desktop.
successfully_sent_countNoThe number of notifications that were sent successfully by Pushpad.
Behavior3/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It adds the 35-day availability constraint, which is valuable. However, it does not mention whether the operation is read-only (though implied by 'GET'), error handling, authentication needs, or what 'stats' entails. The output schema fills some gaps, but the description itself is minimal on behavior.

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 concise at two sentences, front-loading the purpose. The first sentence is slightly verbose ('To get... send a GET request') but remains clear. Every sentence adds value (purpose + constraint). No wasted words.

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 simplicity (one required parameter, output schema present), the description is mostly complete. It explains what the tool does, the API endpoint, and a key temporal constraint. It does not mention prerequisites or error scenarios, but these are less critical for a straightforward get operation.

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?

The input schema covers 100% of parameters with a description for notification_id. The tool description adds no additional meaning beyond the schema—it only refers to the ID in the URL pattern. According to the rubric, with high schema coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'get a notification and its stats'. It uses a specific verb ('get') and resource ('notification'), and distinguishes it from sibling tools like notifications_list (list all) and notifications_create (create). The inclusion of the HTTP endpoint further clarifies the action.

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 implies the tool is for retrieving a single notification by ID, but it does not explicitly compare with alternatives (e.g., 'use this instead of notifications_list when you know the ID'). The 35-day availability constraint is a usage condition, but no guidance on when to use or avoid the tool is provided.

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/pushpad/pushpad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server