@sellable/mcp 0.1.188 → 0.1.189

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/mcp",
3
- "version": "0.1.188",
3
+ "version": "0.1.189",
4
4
  "type": "module",
5
5
  "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
6
6
  "main": "dist/index.js",
@@ -21,7 +21,7 @@ validate-sample tool:
21
21
  get_subskill_prompt({ subskillName: "create-campaign-v2-tail" })
22
22
  ```
23
23
 
24
- CampaignOffer state and watch link are canonical. Resume, gates, and handoffs
24
+ CampaignOffer state and the watch link are canonical. Resume, gating, and handoff
25
25
  read campaign state first: `campaignId`, `watchUrl`, `campaignBrief`,
26
26
  `currentStep`, source/search association, `selectedLeadListId`,
27
27
  `workflowTableId`, `leadScoringRubrics`, `approvedMessageTemplate`,
@@ -164,9 +164,8 @@ does not include `mode`, `workspaceId`, and `token`, recover a fresh link with
164
164
  `create_campaign({ campaignId })` or `get_campaign` before asking for approval.
165
165
  Later normal updates and approval turns must not print `Watch link:`; update
166
166
  `currentStep` and `watchNarration` so the already-open app changes live. Reprint
167
- only if asked or for missing/broken URL recovery. Never call browser-opening
168
- tools, Computer Use, shell `open`, or browser automation just because a watch
169
- link exists.
167
+ only if asked or for missing/broken URL recovery. Never call browser-opening tools,
168
+ Computer Use, shell `open`, or browser automation just because a watch link exists.
170
169
 
171
170
  Every watched step switch must call:
172
171
 
@@ -182,13 +181,13 @@ copy.
182
181
  ## Lead Source
183
182
 
184
183
  Default source order when unspecified: LinkedIn post engagement, Sales Nav
185
- recent activity, broader Sales Nav title search, then Prospeo, unless the
186
- campaign is hiring-led. For hiring-by-role signals, start with Prospeo because
184
+ recent activity, broader Sales Nav title search, then Prospeo. Use that order only
185
+ when not hiring-led. For hiring-by-role signals, start with Prospeo because
187
186
  `search_prospeo` supports `company_job_posting_hiring_for` and
188
- `company_job_posting_quantity`; Sales Nav is only an activity/referral fallback.
187
+ `company_job_posting_quantity`; Sales Nav does not provide hiring-by-role filters.
189
188
 
190
189
  Before any provider prompt/search/scout call, move the watched campaign to
191
- provider/source selection, then show one `## Find Buyers Plan` gate before
190
+ provider/source selection, then show one `## Find Buyers Plan` before
192
191
  `request_user_input`, without repeating the watch URL. The plan must appear in
193
192
  chat before the question. This approval only authorizes finding where to look.
194
193
  It does not add anyone yet. Write: