@sellable/mcp 0.1.107 → 0.1.108

package/dist/tools/sequencer.js

@@ -66,7 +66,9 @@ export const sequencerToolDefinitions = [
         description: "Attach the tier-recommended sequence template to a campaign. " +
             "Delegates template selection to the backend's existing tier-aware selector " +
             "(selectTemplateForTiers), which picks `If Open Profile -> INMAIL_OPEN, else INVITE` " +
-            "for premium/Sales Nav senders and `INVITE -> accepted -> DM` otherwise. " +
+            "for Sales Nav/Recruiter senders and `INVITE -> accepted -> DM` for Basic, Premium, or mixed sender sets. " +
+            "Paid InMail Campaign is not auto-selected because it can spend InMail credits; " +
+            "use attach_sequence with an explicit paid-InMail template only after the user opts in. " +
             "Prefer this over attach_sequence during the create-campaign-v2 autonomous tail — " +
             "it removes the risk of hand-authoring an invalid template mid-long-context. " +
             "Use attach_sequence directly only when the caller needs a custom non-recommended cadence.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.107",
+  "version": "0.1.108",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/core/flow.v2.json

@@ -2192,6 +2192,7 @@
           "requiredVisibleContent": [
             "connect or select a LinkedIn sender",
             "Slack reply review",
+            "Sales Nav vs Premium sequence recommendation, with Paid InMail Campaign only on explicit opt-in",
             "nothing starts until the user confirms launch"
           ],
           "onNoAvailableSender": "surface settings link and wait for sender_connection_required",

package/skills/create-campaign-v2/references/final-handoff-contract.md

@@ -45,9 +45,12 @@ order (all before waiting for the user):
 currentStep: "sequence" })` to attach the sender via the v3 senders route and
    move the watch link to Sequence.
 8. Call `attach_recommended_sequence({ campaignId, currentStep: "send" })` to
-   bind the tier-aware recommended sequence. If that response does not persist
-   `currentStep: "send"`, call `update_campaign({ campaignId, currentStep:
-"send" })`.
+   bind the tier-aware recommended sequence. Explain the sequence choice in the
+   handoff: Sales Nav/Recruiter senders get the Sales Nav Open Profile
+   strategy, Basic/Premium/mixed senders get the Premium invite-to-DM strategy,
+   and Paid InMail Campaign is only an explicit paid-InMail opt-in because it
+   can spend InMail credits. If that response does not persist `currentStep:
+"send"`, call `update_campaign({ campaignId, currentStep: "send" })`.
 9. Re-surface the `watchUrl` using the exact block in
    `references/watch-link-handoff.md`.
 10. Surface the `handoff.orientation` string from `auto-execute.yaml`

package/skills/create-campaign-v2-tail/SKILL.md

@@ -459,7 +459,11 @@ Shape:
 currentStep: "sequence" })` to attach the sender through the v3 senders
    route and orient the watch link to Sequence.
 8. Call `attach_recommended_sequence({ campaignId, currentStep: "send" })`
-   (bind the tier-recommended sequence to the campaign). If the tool response
+   (bind the tier-recommended sequence to the campaign). Explain the sequence
+   choice plainly: Sales Nav/Recruiter senders get the Sales Nav Open Profile
+   strategy, Basic/Premium/mixed senders get the Premium invite-to-DM strategy,
+   and Paid InMail Campaign is available only as an explicit paid-InMail
+   opt-in because it can spend InMail credits. If the tool response
    does not persist `currentStep: "send"`, call
    `update_campaign({ campaignId, currentStep: "send" })`.
 9. Re-surface the `watchUrl` using `references/watch-link-handoff.md`.