@sellable/mcp 0.1.230 → 0.1.231

package/dist/tools/leads.js

@@ -2422,7 +2422,7 @@ function normalizeProspeoCompanySearchInputForMcp(input) {
             removeEmptyObjectFilter(filters, "company_lookalike");
         }
     }
-    relaxMcpDomainSeedMatchAll(filters, seedDomains);
+    relaxMcpSeedMatchAll(filters, seedDomains.length + seedCompanies.length);
     normalizeMcpCompanyKeywords(filters);
     normalizeMcpCompanyWebsiteSearch(filters);
     normalizeMcpCompanyIcp(filters);
@@ -2568,8 +2568,8 @@ function stripMcpDuplicateCompanyIndustry(filters) {
         delete filters.company_industry;
     }
 }
-function relaxMcpDomainSeedMatchAll(filters, seedDomains) {
-    if (seedDomains.length <= 1 || !isPlainObject(filters.company_lookalike)) {
+function relaxMcpSeedMatchAll(filters, seedCount) {
+    if (seedCount <= 1 || !isPlainObject(filters.company_lookalike)) {
         return;
     }
     if (filters.company_lookalike.match_all === true) {

package/package.json

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

package/skills/create-campaign/SKILL.md

@@ -257,7 +257,7 @@ company/domain plus `company_lookalike.minimum_tier` and simple confirmed
 attributes, headcount, or industry. Do not add `company_website_search`,
 `company_keywords`, or `company_icp` until the account sample proves the seed
 works. Do not send placeholder seed names like `another approved best-customer seed`,
-and only use concrete companies or domains you actually resolved. Prefer `seedDomains`
+and only use concrete companies or domains you actually resolved. If another approved seed is referenced but not named, ask for it or run one seed without `match_all`; do not invent a second seed from examples, competitors, or exclusions. Prefer `seedDomains`
 for single-seed lookalikes. For multi-seed `match_all` lookalikes, use concrete company names unless you already know the exact canonical Prospeo domains; 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`
 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.
 Do not use `AI`, `API`, `GTM`, or `SaaS` as company keyword terms.

package/skills/find-leads/SKILL.md

@@ -432,7 +432,7 @@ Use first for broad persona expansion, ABM/domain targeting, hiring-led targetin
   attributes, headcount, or industry. Do not add `company_website_search`,
   `company_keywords`, or `company_icp` until the account sample proves the seed
   works. Do not send placeholder seed names like `another approved best-customer seed`,
-  and only use concrete companies or domains you actually resolved. Prefer `seedDomains`
+  and only use concrete companies or domains you actually resolved. If another approved seed is referenced but not named, ask for it or run one seed without `match_all`; do not invent a second seed from examples, competitors, or exclusions. Prefer `seedDomains`
   for single-seed lookalikes. For multi-seed `match_all` lookalikes, use concrete company names unless you already know the exact canonical Prospeo domains; 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` 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.
 - Do not use `company_intent`. Do not invent unsupported support-channel filters

package/skills/providers/prospeo.md

@@ -109,6 +109,9 @@ Avoidable-400 guardrails:
 - 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.
 - 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.
 - Do not send placeholder seed names such as `another approved best-customer seed`; use only concrete company names or domains you have actually resolved.
+- If the user references another approved seed but does not name it, ask for the
+  seed or run a one-seed lookalike without `match_all`; do not invent a second
+  seed from examples, competitors, or exclusions.
 - Prefer seed domains for single-seed lookalikes. For multi-seed `match_all`
   lookalikes, use concrete company names unless you already know the exact
   canonical Prospeo domains; guessed product or marketing domains can 400 with
@@ -259,6 +262,8 @@ Preference rules:
 - 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.
 - 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.
 - For seeded lookalikes, avoid first-call `has_api` + `has_sso`; use one confirmed attribute first, then refine.
+- Do not invent missing approved seeds. If a second seed is not named, ask for it
+  or run one seed without `match_all`.
 - Prefer `seedDomains` for single-seed lookalikes. For multi-seed `match_all`
   lookalikes, use concrete company names unless you know the exact canonical
   Prospeo domains; do not mix both in one seeded lookalike call.