Skip to main content
Glama
pushengage-mcp

pushengage-mcp

Resend a sent notification

pushengage_resend_notification

Resend an already-sent push notification to its original audience exactly as stored, creating a new notification and returning its ID. Use to repeat a past send without changing content.

Instructions

Sends an already-sent notification again, exactly as stored — the content cannot be changed on the way out, because the API re-reads the notification itself. Resending creates a NEW notification: the response reports its id, with the original as resent_from. Only works on a notification that has already been sent. To send a draft or a scheduled one now, use pushengage_update_notification with status="sent"; to send a changed copy, use pushengage_duplicate_notification. Subscriber-timezone sends cannot be resent, nor can a single A/B variant or a drip or triggered campaign notification. Each call dispatches a real push to the notification's original audience, so confirm with the user before calling it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notification_id": "<notification_id>"
    },
    "name": "pushengage_resend_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoOverride the currently selected site
notification_idYesThe notification to act on. Get it from pushengage_list_notifications, or from the notification_id a send tool returned.

Output Schema

NameRequiredDescriptionDefault
resentNo
view_urlNo
notification_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: content is immutable because the API re-reads the stored notification, the call creates a NEW notification whose id is returned with `resent_from` linking the original, and each call dispatches a real push to the original audience — a non-idempotent side effect that the `idempotentHint: false` annotation only hints at. The unsupported notification classes are also disclosed, which annotations cannot convey.

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?

Front-loaded with the core semantics and no filler sentences; every clause carries information. It is delivered as one dense block mixing semantics, exclusions, alternatives, and a safety warning, which would read better as separated lines, but nothing is redundant.

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?

An output schema exists, and the description still notes the key return fact (new id plus `resent_from`) so the agent understands the outcome shape without consulting it. Combined with the mutation semantics, exclusions, and audience-blast warning, nothing needed to invoke this correctly is missing.

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 both `notification_id` and the `site_id` override are already documented in the schema, including where to obtain the id. The description adds only the framing that the notification is re-read as stored; it says nothing further about the site override or id formats, so baseline 3 applies.

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?

"Sends an already-sent notification again, exactly as stored" names a specific verb, resource, and precondition, and immediately clarifies that it is not the same as sending a draft or a changed copy. An agent can distinguish it from pushengage_send_notification, pushengage_update_notification, and pushengage_duplicate_notification without opening any 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?

Explicit when-to-use (already-sent notifications only), explicit alternatives for adjacent cases (update_notification with status="sent" for drafts/scheduled, duplicate_notification for a changed copy), and explicit exclusions (subscriber-timezone sends, single A/B variants, drip and triggered campaign notifications). It also states the confirmation requirement before calling.

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