git:20260917.1ca941b to git:20261008.74c0980

15 added, 17 removed. Audit A to A.

---

name: adsagent-notifications

- description: Use when viewing or configuring AdsAgent notifications, email, Feishu, Telegram, or Meta Ads Webhooks.

+ description: Use when inspecting AdsAgent notifications, requesting an alert refresh, or explaining MCP Events and retired integrations.

---

# AdsAgent Notifications

- 1. For alert status, use `notifications_list`. List

- integrations and read runtime monitoring capabilities when inspecting

- configuration or describing coverage.

- 2. Use only masked destinations, public refs, and operator-scoped advertised

- tools. Never solicit hidden credentials in chat.

- 3. For integration changes or test delivery, prepare exactly one action, show

- the sanitized summary, obtain explicit approval, and confirm once.

- 4. `notifications_scan` updates alerts and may queue delivery to configured

- external channels. Use it only for a requested or already authorized alert

- refresh, with that effect clear; it is not a read-only status check and has

- no separate prepare/confirm pair.

- 5. Poll any returned task and distinguish provider acceptance from observed

- destination delivery.

- 6. Never replay an uncertain confirm or change customer FB User permissions.

+ 1. For Meta alert status, use `notifications_list` or `notifications_summary`.

+ Inspect returned monitoring capabilities before describing coverage.

+ 2. Current Meta MCP no longer configures email, Feishu, Telegram, or Meta Ads

+ Webhooks. Explain that boundary; never collect integration credentials or

+ invent configuration tools.

+ 3. `notifications_scan` changes alert state and may generate MCP Events. Use

+ it only for a requested or already authorized alert refresh, with that

+ effect clear; it is not a read-only status check and has no separate

+ prepare/confirm pair.

+ 4. MCP Events require advertised server and client support. An event carries

+ references, not approval or proof of completion; read the referenced state.

+ 5. Acknowledge or resolve an alert only when requested. Never replay an

+ uncertain change or modify customer FB User permissions.

Read [monitoring-contract.md](monitoring-contract.md) only when explaining

- event coverage, thresholds, channel configuration, webhook subscription, test

- delivery, or recovery.

+ event coverage, thresholds, retired integrations, push support, or recovery.

[Data boundary](data-boundary.md) applies.