@sellable/mcp 0.1.221 → 0.1.222

package/dist/tools/leads.js

@@ -453,7 +453,7 @@ For awards: { "company_awards": { "include": ["G2"], "match_mode": "CONTAINS" }
 For website traffic: { "company_website_traffic": { "min_monthly_visits": 50000 } }.
 For products/services, integrations, key customers, and Google discovery use "company_products_services", "company_integrations", "company_key_customers", and "company_google_discovery".
 For headcount by location: { "company_headcount_by_location": { "entries": [{ "country": "United States", "city": "Austin", "min_headcount": 10 }] } }.
-For structured ICP: { "company_icp": { "titles_include": ["Head of RevOps"], "company_sizes": ["midmarket"], "departments": { "include": ["Sales"], "match_mode": "ANY" } } }.
+For structured ICP: { "company_icp": { "titles_include": ["Head of RevOps"], "company_sizes": ["midmarket"], "departments": { "include": ["Sales"], "match_mode": "ANY" } }, "company_headcount_range": ["101-200", "201-500", "501-1000"] }. Pair company_icp.company_sizes with company_headcount_range or rely on MCP normalization that derives the range; inspect the account sample for size drift.
 company_intent is unsupported; support-channel AI Attribute guesses like phone/email/chat/ticket/social are not exposed. public API rows do not include lookalike tier/score/reason.`;
 function loadSignalDiscoveryConfig() {
     if (!existsSync(signalProviderConfigPath)) {

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -218,6 +218,18 @@ reconstruct raw account rows or domains manually. Account rows are not people
 leads yet. The confirmation creates the `domainFilterId` that constrains the
 follow-on `search_prospeo` people search.
 
+Prospeo company/account search is useful when the source plan depends on
+website traffic (`company_website_traffic`), confirmed AI Attributes including
+`pricing`, `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`,
+`has_open_source`, `has_marketplace`, `has_blog`, `has_knowledge_base`,
+`has_soc2`, `data_residency: "EU"`, news, awards, website pages, products,
+integrations, key customers, Google discovery, location headcount, or
+structured ICP. When using `company_icp.company_sizes` for micro/SMB/midmarket
+or enterprise sizing, pair it with `company_headcount_range` or rely on the MCP
+normalization that derives the range; inspect the sample for size drift. Do not
+use `company_intent`, and do not invent unsupported support-channel filters or
+AI Attribute guesses like phone/email/chat/ticket/social.
+
     After scouting, ask for a second approval on Start Import. For
     LinkedIn engagement (`signal-discovery` internally), name how many
     recommended posts will be scraped and the target engager/source-candidate

package/skills/find-leads/SKILL.md

@@ -391,6 +391,18 @@ Use first for broad persona expansion, ABM/domain targeting, hiring-led targetin
 - For companies like X, our best customers, lookalike accounts, companies that use AI, companies with API/SSO/Chrome extension, or
   news/award/integration/key-customer account filters, use
   `search_prospeo_companies` before people search.
+- Use Prospeo company/account search when the ask depends on website traffic
+  (`company_website_traffic`), confirmed AI Attributes including `pricing`,
+  `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`, `has_open_source`,
+  `has_marketplace`, `has_blog`, `has_knowledge_base`, `has_soc2`,
+  `data_residency: "EU"`, website pages, products, integrations, key
+  customers, Google discovery, location headcount, or structured ICP.
+- When using `company_icp.company_sizes` for micro/SMB/midmarket or enterprise
+  sizing, pair it with `company_headcount_range` or rely on MCP normalization
+  that derives the range; inspect the account sample for size drift before
+  approving accounts.
+- Do not use `company_intent`. Do not invent unsupported support-channel filters
+  or AI Attribute guesses like phone/email/chat/ticket/social.
 - Company/account search returns an account sample only; account rows are not people leads yet. Ask the user to approve the account sample.
 - After approval, call `confirm_prospeo_company_accounts` with the
   `companySearchToken` and selected Prospeo company IDs from

package/skills/providers/prospeo.md

@@ -58,6 +58,7 @@ search_prospeo_companies({
       "company_sizes": ["midmarket"],
       "departments": { "include": ["Sales"], "match_mode": "ANY" }
     },
+    "company_headcount_range": ["101-200", "201-500", "501-1000"],
     "company_website_traffic": { "min_monthly_visits": 50000 },
     "company_key_execs": {
       "event_types": ["VP of Sales Appointed"],
@@ -79,6 +80,12 @@ confirm_prospeo_company_accounts({
 
 Use the returned `domainFilterId` in `search_prospeo` with people filters. Do not reconstruct raw account rows or domains manually as Prospeo-sourced provenance.
 
+For structured ICP sizing, pair `company_icp.company_sizes` with
+`company_headcount_range` when possible. The MCP normalizer derives headcount
+ranges for `micro`, `smb`, `midmarket`, `enterprise`, and `large_enterprise`
+when no explicit headcount range is supplied, but the sample should still be
+checked for size drift before accounts are approved.
+
 Unsupported/caveats:
 
 - `company_intent` is unsupported by Prospeo public API.
@@ -86,7 +93,7 @@ Unsupported/caveats:
 - Public API account rows do not expose row-level lookalike tier/score/reason; do not fabricate them.
 - Website traffic and key executive filters are experimental and may fail by account/API policy.
 
-Confirmed AI Attribute keys:
+The confirmed AI Attributes keys are:
 
 - `demo`
 - `freetrial`