@sequenzy/mcp 0.0.162 → 0.0.164

package/README.md

@@ -64,6 +64,8 @@ except for six operations: `connect_integration`, `create_api_key`,
 `rotate_sequence_inbound_webhook_secret`. Feedback stays available with a
 reduced schema for generalized, explicitly requested product feedback.
 
+Tool annotations disclose supported replacement and irreversible-delivery modes, including automation-triggering actions. Public content and provider changes are marked open-world; private draft creation and additive notes remain non-destructive. Feedback goes to the Sequenzy team through Telegram with the authenticated company name/ID and account email added for attribution, which clients must disclose before sending.
+
 Remote clients should authenticate with the Sequenzy OAuth flow when supported. Local and automation clients can still use the stdio package below with `SEQUENZY_API_KEY`.
 
 The hosted endpoint and the stdio package support MCP specification
@@ -326,8 +328,8 @@ build a list as well as create it. Imports that apply `listIds` also need
 
 ## Tools
 
-The standard surface currently exposes 243 MCP tools. The OpenAI-reviewed
-surface exposes 237; only the six operations listed above are omitted.
+The standard surface currently exposes 252 MCP tools. The OpenAI-reviewed
+surface exposes 246; only the six operations listed above are omitted.
 
 Tools reject arguments they do not declare instead of silently ignoring them.
 Errors name the unsupported fields, list the supported arguments, and provide
@@ -1639,3 +1641,25 @@ You can invite a `marketer` to manage subscribers, marketing campaigns and seque
 Use `get_email_ai_style` to inspect the company's saved appearance and `revisionId`. `save_email_ai_style` captures an existing email by its underlying `emailId`; pass `expectedStyleId: null` only for an initial save, or the reviewed revision when replacing. Optional `canvas` captures an unsaved editor snapshot containing `blocks`, `theme`, `fontFamily`, and `emailPreset`. Saving also detects layout habits (for example dotted dividers around every button) and keeps all of them unless `layoutRuleIds` lists the rule IDs to keep (`[]` keeps none); optional `notes` (500 characters max) adds design guidance. Review `style.layout.rules` in the response. `clear_email_ai_style` requires the current nonempty revision.
 
 Reads require `emails:read`; saves/clears require `emails:write` and the current workspace role. Marketers cannot capture transactional source emails. A 409 conflict requires reading and reviewing the new state before retrying. These tools never edit or send the source email. Generation across all surfaces uses the saved default unless explicit styling or a plain-text choice takes precedence.
+
+### Background contact tasks
+
+Use `start_subscriber_operation` to add tags to an entire filtered contact
+audience. Supply `kind: "add_tags"`, `tags` and `requestKey`; reuse the same
+key/settings after an uncertain response. `list_subscriber_operations`,
+`get_subscriber_operation` and `cancel_subscriber_operation` provide the same
+progress and cancellation workflow as Contacts.
+
+All operations require `subscribers:read`; tagging additionally requires
+`subscribers:tag`, new tag definitions require `tags:write`, and
+`triggerAutomations: true` requires `automations:trigger`. Automation triggering
+defaults to false. Existing synchronous bulk tag tools remain available for up
+to 500 explicit contacts. Background audiences accept up to 1,000 explicit IDs,
+or live filters/list/search criteria without a total audience limit.
+
+Selection walks live pages before tagging and excludes contacts created after
+the request. It is not a point-in-time snapshot. Inspect `failed` and `failures`
+even when status is completed. Interrupted in-flight tag actions are reported
+as uncertain and never automatically replayed; reconcile those contacts before
+starting another task. Cancellation retains applied changes. Active tasks have
+a seven-day processing deadline; terminal records are retained for seven days.