@sellable/mcp 0.1.228 → 0.1.229
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/dist/tools/leads.js
CHANGED
|
@@ -2581,6 +2581,16 @@ function stripMcpSeededLookalikeRiskyRefinements(filters, hasSeeds) {
|
|
|
2581
2581
|
delete filters.company_icp;
|
|
2582
2582
|
delete filters.company_keywords;
|
|
2583
2583
|
delete filters.company_website_search;
|
|
2584
|
+
simplifyMcpSeededLookalikeAttributes(filters);
|
|
2585
|
+
}
|
|
2586
|
+
function simplifyMcpSeededLookalikeAttributes(filters) {
|
|
2587
|
+
const attributes = filters.company_attributes;
|
|
2588
|
+
if (!isPlainObject(attributes)) {
|
|
2589
|
+
return;
|
|
2590
|
+
}
|
|
2591
|
+
if (attributes.has_api === true && attributes.has_sso === true) {
|
|
2592
|
+
delete attributes.has_sso;
|
|
2593
|
+
}
|
|
2584
2594
|
}
|
|
2585
2595
|
function stripMcpKeyCustomerCompanionFilters(filters) {
|
|
2586
2596
|
const keyCustomers = filters.company_key_customers;
|
package/package.json
CHANGED
|
@@ -258,7 +258,8 @@ attributes, headcount, or industry. Do not add `company_website_search`,
|
|
|
258
258
|
`company_keywords`, or `company_icp` until the account sample proves the seed
|
|
259
259
|
works. Do not send placeholder seed names like `another approved best-customer seed`,
|
|
260
260
|
and only use concrete companies or domains you actually resolved. Prefer `seedDomains`
|
|
261
|
-
over `seedCompanies`; do not mix both in one seeded lookalike call. Do not
|
|
261
|
+
over `seedCompanies`; do not mix both in one seeded lookalike call. Do not combine `has_api` and `has_sso` in the first seeded lookalike call; start with `has_api`
|
|
262
|
+
and refine after a valid account sample if SSO still matters. Do not send `company_website_search.exclude_keywords` without a positive website include signal.
|
|
262
263
|
Do not use `AI`, `API`, `GTM`, or `SaaS` as company keyword terms.
|
|
263
264
|
Do not combine `company_key_customers` with ICP, website-search, keyword,
|
|
264
265
|
attribute, industry, or headcount filters until the standalone pass proves
|
|
@@ -433,7 +433,8 @@ Use first for broad persona expansion, ABM/domain targeting, hiring-led targetin
|
|
|
433
433
|
`company_keywords`, or `company_icp` until the account sample proves the seed
|
|
434
434
|
works. Do not send placeholder seed names like `another approved best-customer seed`,
|
|
435
435
|
and only use concrete companies or domains you actually resolved. Prefer `seedDomains`
|
|
436
|
-
over `seedCompanies`; do not mix both in one seeded lookalike call. Do not
|
|
436
|
+
over `seedCompanies`; do not mix both in one seeded lookalike call. Do not combine `has_api` and `has_sso` in the first seeded lookalike call; start with
|
|
437
|
+
`has_api` and refine after a valid account sample if SSO still matters. Do not send `company_website_search.exclude_keywords` without a positive website include signal.
|
|
437
438
|
- Do not use `company_intent`. Do not invent unsupported support-channel filters
|
|
438
439
|
or AI Attribute guesses like phone/email/chat/ticket/social.
|
|
439
440
|
- Company/account search returns an account sample only; account rows are not people leads yet. Ask the user to approve the account sample.
|
|
@@ -107,6 +107,7 @@ Avoidable-400 guardrails:
|
|
|
107
107
|
- Do not send `company_keywords.exclude` unless at least one include keyword is present.
|
|
108
108
|
- Do not duplicate `company_industry` when `company_icp.industries` already carries the industry.
|
|
109
109
|
- For seeded company lookalikes, keep the first call simple: seed company/domain + `company_lookalike.minimum_tier` + confirmed attributes, headcount, or industry. Do not add `company_website_search`, `company_keywords`, or `company_icp` until the account sample proves the seed works.
|
|
110
|
+
- For seeded company lookalikes, do not combine `has_api` and `has_sso` in the first call; start with `has_api` and refine after a valid account sample if SSO still matters.
|
|
110
111
|
- Do not send placeholder seed names such as `another approved best-customer seed`; use only concrete company names or domains you have actually resolved.
|
|
111
112
|
- Prefer seed domains over seed company names. Do not mix `seedDomains` and `seedCompanies` in the same lookalike call; use concrete domains when available.
|
|
112
113
|
- Do not send `company_website_search.exclude_keywords` without a positive website include signal.
|
|
@@ -254,6 +255,7 @@ Preference rules:
|
|
|
254
255
|
- Do not use `AI`, `API`, `GTM`, or `SaaS` as company keyword terms; use longer phrases such as `artificial intelligence`, `application programming interface`, `go to market`, or `software as a service`.
|
|
255
256
|
- Run `company_key_customers` as a standalone first-pass filter. Do not combine `company_key_customers` with ICP, website-search, keyword, attribute, industry, or headcount filters until the standalone pass proves useful.
|
|
256
257
|
- For seeded lookalikes, avoid first-call `company_website_search`, `company_keywords`, and `company_icp`; use resolved seeds plus lookalike tier and simple attributes/headcount/industry first.
|
|
258
|
+
- For seeded lookalikes, avoid first-call `has_api` + `has_sso`; use one confirmed attribute first, then refine.
|
|
257
259
|
- Prefer `seedDomains` over `seedCompanies`; do not mix both in one seeded lookalike call.
|
|
258
260
|
|
|
259
261
|
### Person Filters
|