Skip to main content
Glama
pushpad

Pushpad MCP

Official
by pushpad

notifications_create

Create and send a web push notification to specific users, segments, or all subscribers. Target by user IDs, tags, or boolean expressions, and customize with title, body, images, actions, and scheduling.

Instructions

To send a web push notification, send a POST request to /projects/PROJECT_ID/notifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNoThe number of seconds after which the notification should be dropped if the device of the user is offline.
bodyYesThe 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.
image_urlNoThe url of an image that will be displayed in the notification content. Suggested size: 800px for the longer side.
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.
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.
project_id__pathYesThe ID of a project. (Path parameter)
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe notification id.
uidsNoThis field is included in the response only if you specify some user IDs (uids) in the request, and it indicates which of those users are subscribed to notifications. This field is not available for scheduled notifications.
send_atNoThe time when the notification will be sent. Available only for scheduled notifications.
scheduledNoThe number of devices the notification will be delivered to. Note that this value may differ from the number of user IDs (uids) in the request, for example when some users are not subscribed or are subscribed with multiple devices. This field is not available for scheduled notifications.
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'send a POST request to /projects/PROJECT_ID/notifications', which is an HTTP method and endpoint. It does not mention that the tool requires a project_id, that it is a write operation, whether it is idempotent, any authentication needs, rate limits, or side effects (e.g., duplicate notifications if called multiple times). This is a critical gap for a tool with 18 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence), but it sacrifices completeness. It is front-loaded with the purpose, but the structural choice to include an HTTP endpoint (which is an implementation detail) and omit key context makes it less effective. Every sentence should earn its place; this one does partially but leaves major gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (18 parameters, nested objects, required fields, output schema), the description is insufficient. It does not explain the overall workflow, how to use tags vs uids, or what the output indicates (e.g., created notification ID). The output schema exists but the description should still provide a high-level summary. The rich schema compensates partially, but the description is too sparse.

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 has 100% description coverage, documenting all 18 parameters with examples and detailed explanations. The tool description adds no additional parameter meaning beyond what the schema provides. Baseline 3 is appropriate because the schema carries the full burden of parameter semantics.

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: 'send a web push notification'. The verb 'send' and resource 'web push notification' are specific. It differentiates from siblings like notifications_get (retrieve) and notifications_cancel (cancel) by focusing on creation/sending.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool ('To send a web push notification'), but provides no guidance on when not to use it, exclusions, or alternatives. With siblings like notifications_cancel, it would be helpful to mention that this tool creates a notification, not cancels one. No context is given about prerequisites or when to prefer other tools.

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