Skip to main content
Glama

PushNotif Official MCP Server

by io.github.AarsyDesign
OverviewDiscussionsAdmin

send_push_notification

Broadcast an immediate push notification across Web Push (VAPID), Android (FCM), and iOS (APNs) to active subscribers of a specific app_id. Use this tool for instant real-time delivery; do not use it for future or recurring broadcasts (use schedule_push_notification instead) or on-site HTML popups (use configure_inapp_banner instead). Prerequisite: call list_apps first to obtain app_id. Requires PUSHNOTIF_API_KEY, deducts 1 credit (Rp 0.20) per successfully delivered device (0 credits charged for 404/410 dead tokens, which are auto-pruned), and is irreversible once dispatched; when segment is set to a custom tag (from update_subscriber_tags) instead of 'all', only subscribers carrying that tag receive the broadcast, and omitting url defaults the tap action to the app's registered site_url. Returns JSON { ok, campaign_id, total_targeted, total_delivered, total_gone_pruned, credits_deducted, credits_remaining }.

Input Schema

NameRequiredDescriptionDefault
urlNoOptional HTTPS destination URL opened when the notification is tapped (defaults to app's site_url)
bodyYesNotification message body text (1 to 240 characters)
titleYesNotification headline shown on the lock screen (1 to 100 characters)
app_idYesTarget application ID in format app_xxxx (obtain from list_apps)
segmentNoTarget audience filter: 'all' (default) or a specific subscriber/merchant tag assigned via data-tags, PushNotif.addTag(), or update_subscriber_tags
icon_urlNoOptional HTTPS URL of a custom notification icon/logo (e.g., per-merchant logo override on a shared App ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / icon_url
      Added value: +{
+  "description": "Optional HTTPS URL of a custom notification icon/logo (e.g., per-merchant logo override on a shared App ID)",
+  "type": "string"
+}
    • changedInput schema / properties / segment / description
      Previous value: -"Target audience filter: 'all' (default) or a specific subscriber tag assigned via update_subscriber_tags"New value: +"Target audience filter: 'all' (default) or a specific subscriber/merchant tag assigned via data-tags, PushNotif.addTag(), or update_subscriber_tags"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already indicate a non-read-only, non-idempotent, open-world operation, and the description adds substantial behavioral context beyond them: required PUSHNOTIF_API_KEY, credit cost per delivered device with dead-token exceptions, irreversibility after dispatch, and segment-specific delivery behavior. There is no contradiction with the annotations.

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 purpose and exclusions are front-loaded, and the description is dense with useful operational details. However, it is a long single paragraph that could be easier to scan if broken into shorter sentences or sections.

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

Completeness5/5

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

For a complex, irreversible mutation tool with billing and authentication implications, the description covers prerequisites, costs, side effects, segment behavior, defaults, and the return payload fields. Since no output schema exists, including the JSON return shape is especially valuable.

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?

Schema description coverage is 100%, so all six parameters are already documented in the schema. The description reinforces a few semantic details, such as segment filtering and the url default, but mostly repeats information already present in the parameter descriptions rather than adding significant new meaning.

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 states a specific verb and resource: broadcast an immediate push notification across Web Push, Android, and iOS to active subscribers of a specific app_id. It clearly distinguishes itself from schedule_push_notification and configure_inapp_banner, so an agent can identify its purpose without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool (instant real-time delivery) and when not to use it, naming the alternatives for future/recurring broadcasts and on-site HTML popups. It also includes the prerequisite to call list_apps first to obtain app_id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PushNotif Official MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources