@sellable/install 0.1.165 → 0.1.167
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/bin/sellable-install.mjs
CHANGED
|
@@ -585,6 +585,8 @@ const CREATE_CAMPAIGN_ALLOWED_TOOLS = [
|
|
|
585
585
|
"mcp__sellable__lookup_sales_nav_filter",
|
|
586
586
|
"mcp__sellable__search_sales_nav",
|
|
587
587
|
"mcp__sellable__search_prospeo",
|
|
588
|
+
"mcp__sellable__search_prospeo_companies",
|
|
589
|
+
"mcp__sellable__confirm_prospeo_company_accounts",
|
|
588
590
|
"mcp__sellable__search_signals",
|
|
589
591
|
"mcp__sellable__fetch_post_engagers",
|
|
590
592
|
"mcp__sellable__enrich_with_prospeo",
|
package/package.json
CHANGED
|
@@ -25,6 +25,8 @@ allowed-tools:
|
|
|
25
25
|
- mcp__sellable__lookup_sales_nav_filter
|
|
26
26
|
- mcp__sellable__search_sales_nav
|
|
27
27
|
- mcp__sellable__search_prospeo
|
|
28
|
+
- mcp__sellable__search_prospeo_companies
|
|
29
|
+
- mcp__sellable__confirm_prospeo_company_accounts
|
|
28
30
|
- mcp__sellable__search_signals
|
|
29
31
|
- mcp__sellable__fetch_post_engagers
|
|
30
32
|
- mcp__sellable__enrich_with_prospeo
|
|
@@ -204,6 +206,30 @@ are likely. Sales Nav is useful for recent LinkedIn activity, role/title
|
|
|
204
206
|
precision, and referral paths, but it does not provide hiring-by-role filters;
|
|
205
207
|
say that distinction plainly in the source-plan gate.
|
|
206
208
|
|
|
209
|
+
For company lookalikes, best-customer lookalikes, "companies like X",
|
|
210
|
+
lookalike accounts, companies that use AI, companies with API/SSO/Chrome
|
|
211
|
+
extension, news/award/integration/key-customer filters, or account discovery
|
|
212
|
+
before person search, use the Prospeo account approval flow:
|
|
213
|
+
`search_prospeo_companies -> confirm_prospeo_company_accounts -> search_prospeo`.
|
|
214
|
+
First return an account sample and ask the user to approve the account set.
|
|
215
|
+
Only call `confirm_prospeo_company_accounts` with the `companySearchToken`
|
|
216
|
+
returned by `search_prospeo_companies` and selected Prospeo company IDs; never
|
|
217
|
+
reconstruct raw account rows or domains manually. Account rows are not people
|
|
218
|
+
leads yet. The confirmation creates the `domainFilterId` that constrains the
|
|
219
|
+
follow-on `search_prospeo` people search.
|
|
220
|
+
|
|
221
|
+
Prospeo company/account search is useful when the source plan depends on
|
|
222
|
+
website traffic (`company_website_traffic`), confirmed AI Attributes including
|
|
223
|
+
`pricing`, `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`,
|
|
224
|
+
`has_open_source`, `has_marketplace`, `has_blog`, `has_knowledge_base`,
|
|
225
|
+
`has_soc2`, `data_residency: "EU"`, news, awards, website pages, products,
|
|
226
|
+
integrations, key customers, Google discovery, location headcount, or
|
|
227
|
+
structured ICP. When using `company_icp.company_sizes` for micro/SMB/midmarket
|
|
228
|
+
or enterprise sizing, pair it with `company_headcount_range` or rely on the MCP
|
|
229
|
+
normalization that derives the range; inspect the sample for size drift. Do not
|
|
230
|
+
use `company_intent`, and do not invent unsupported support-channel filters or
|
|
231
|
+
AI Attribute guesses like phone/email/chat/ticket/social.
|
|
232
|
+
|
|
207
233
|
After scouting, ask for a second approval on Start Import. For
|
|
208
234
|
LinkedIn engagement (`signal-discovery` internally), name how many
|
|
209
235
|
recommended posts will be scraped and the target engager/source-candidate
|