Skip to main content
Glama
pushengage-mcp

pushengage-mcp

Edit a notification

pushengage_update_notification
Destructive

Edit an existing draft, scheduled, or recurring PushEngage notification by passing only the fields to change; use it to fix titles, timing, or audience without creating a new push.

Instructions

Edits an existing draft, scheduled or recurring notification. Pass notification_id plus ONLY the fields to change — everything else is carried over from the notification as it stands. Use this instead of pushengage_send_notification when the user wants to fix or adjust something already created ("change the title", "move it to 9am", "target a different segment"); use pushengage_send_notification to create something new. Cannot edit a notification that has already been sent or is sending, an RSS auto-push notification, or any part of an A/B test (editing one through the API breaks the test, so it is refused). Nor a notification belonging to a drip or triggered campaign, or one timezone's copy of a subscriber-timezone broadcast — manage those from the campaign or the parent. Editing a PAUSED recurring notification resumes it — the API sets the status back to running on save, exactly as the dashboard does — so tell the user that before editing one. Changing the audience replaces it entirely: pass audience_groups or subscriber_filter to set a new one. A notification with no audience goes to all subscribers — the dashboard calls that "All Subscribers" — and editing one is allowed; the response reports the audience that was saved either way, and names any audience group the API dropped because it no longer exists — the send then reaches all subscribers, so tell the user. Do not add optional fields unless the user explicitly asks to change them.

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_update_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoDestination URL when the subscriber clicks the notification
tagsNoUp to 5 tags, 36 chars each. Only when the user explicitly asks for tags.
titleNoNotification title
statusNoChange the delivery state. Omit to leave it as it is. Set "sent" to send a draft or a scheduled notification now, or "schedule" with a schedule_date to move it.
actionsNoAction buttons. Only when the user explicitly asks.
messageNoNotification message body
site_idNoOverride the currently selected site
ios_pushNoiOS-specific options. Only when the user explicitly asks.
expire_inNoExpiry in seconds (60–2419200). Only when the user explicitly asks.
image_urlNoSmall notification icon. Only when the user explicitly asks for an image.
utm_paramsNoUTM tracking params. Only when the user explicitly asks.
android_pushNoAndroid-specific options. Requires channel_id when set. Only when the user explicitly asks.
big_image_urlNoLarge hero image. Only when the user explicitly asks for a big image.
schedule_dateNoRequired when status is "schedule". Format: YYYY-MM-DD HH:mm:ss in the site timezone.
audience_groupsNoSend to one or more predefined audience groups (1-20 group IDs). Each ID refers to an audience group already configured in PushEngage. Omit this field to send to all subscribers. Only set this when the user mentions a saved/predefined audience group. Mutually exclusive with subscriber_filter.
notification_idYesThe notification to edit. Get it from pushengage_list_notifications, or from the notification_id a send tool returned.
schedule_timezoneNoOPTIONAL. The IANA timezone that `schedule_date` is written in, e.g. "Asia/Kolkata" or "America/New_York". Set this whenever the user names a timezone, or when you know their timezone differs from the site's — the notification is then scheduled for the instant they actually meant, and the response reports both wall clocks so you can tell them what was scheduled. Omit it and `schedule_date` is taken as the SITE's local time, which is what the API assumes. Requires schedule_date; cannot be combined with recurring_schedule, nor with send_in_subscribers_timezone (that flag already makes schedule_date each subscriber's own local time, so there is nothing to convert). Must be a full IANA zone name — abbreviations like "IST", "PST" or "EST" are ambiguous and are rejected, as are the Etc/GMT±N zones, whose sign is inverted.
subscriber_filterNoOPTIONAL. The dashboard's "Send to Custom Audience": personalize who receives this notification based on segments, location, device and more. Mutually exclusive with audience_groups; omit both for "Send to All Subscribers". A 2-D expression: `value` is a list of rule-groups, rules inside a group are AND-ed, and the top-level `op` combines the groups ("or" by default). Segment rules accept segment NAMES and are resolved automatically, so { field: "segments", op: "in", value: ["Sports Fans"] } works without a lookup. For country, state, city, device or device_type values call pushengage_list_audience_filter_values first; for an attributes rule's `key` call pushengage_list_attributes first. Both are site-specific, and a guessed value saves successfully but reaches the wrong people. Every segment reference and attribute key is verified before anything is sent; an unresolvable one fails the call rather than silently changing who receives the push. Example — mobile subscribers in the Sports Fans segment: { op: "or", value: [[{ field: "segments", op: "in", value: ["Sports Fans"] }, { field: "device", op: "in", value: ["mobile"] }]] }. Example — subscribed in the last 7 days on a paid plan: { op: "or", value: [[{ field: "ts_created", op: "ts_elapsed_lt", value: 10080 }, { field: "attributes", key: "plan", op: "ne", value: "free" }]] }.
recurring_scheduleNoOPTIONAL. Turns this into a recurring notification that fires on the chosen days/times between start_date and end_date. Mutually exclusive with status="schedule", schedule_date, and send_in_subscribers_timezone. With recurring_schedule set, leave status at "sent" (default) to activate the recurrence, or use "draft" to save without activating. Only set this when the user explicitly asks for a recurring/repeating notification.
send_in_subscribers_timezoneNoOnly valid when status="schedule" (and not combined with recurring_schedule). When true, schedule_date is interpreted in each subscriber's local timezone instead of the site timezone — one delivery is scheduled per subscriber timezone so every recipient receives the push at the same wall-clock time. Only set this when the user explicitly asks for subscriber-timezone delivery (for example: "send at 9am in their timezone").

Output Schema

NameRequiredDescriptionDefault
urlNo
titleNo
statusNo
messageNo
view_urlNo
notification_idNo
schedule_conversionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial behavioral context they cannot carry: unsent fields are carried over, editing a PAUSED recurring notification silently resumes it and the user must be warned, changing the audience replaces it wholesale, and a dropped audience group causes the send to reach all subscribers. These are exactly the side effects an agent must surface before invoking a destructive mutation.

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 correctly — purpose and the send_notification alternative come first, then exclusions, then side effects. The middle is a dense run-on paragraph of exceptions that would scan faster as a list, but no sentence is filler; each names a distinct restriction or consequence.

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 20-parameter mutation with nested audience and schedule objects and an output schema (so return values need not be described), the description covers everything an agent could get wrong: state restrictions, A/B test breakage, campaign-owned notifications, the paused-recurring resume trap, audience replacement and group-dropping. What remains is per-field detail already fully documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still earns above that by explaining partial-update semantics ("ONLY the fields to change — everything else is carried over"), the replacement-not-merge behavior of audience_groups/subscriber_filter, the All Subscribers default when no audience is set, and the instruction not to add optional fields unless explicitly requested. It does not restate the schedule_timezone vs subscriber_filter timezone distinction, which the schema already handles in depth.

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?

"Edits an existing draft, scheduled or recurring notification" gives a specific verb, resource, and the exact set of editable states, which immediately separates it from delete/duplicate/resend siblings. The second clause clarifies it is a partial-update operation (notification_id plus only changed fields).

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?

Explicitly routes the agent: use this instead of pushengage_send_notification for fixing something already created, with quoted user phrasings ("change the title", "move it to 9am") as triggers. It also enumerates when NOT to use it — sent/sending notifications, RSS auto-push, any part of an A/B test, drip or triggered campaigns, and a single timezone copy of a subscriber-timezone broadcast — and names the correct escalation path (manage those from the campaign or the parent).

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