@sellable/mcp 0.1.59 → 0.1.60
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
|
@@ -279,6 +279,9 @@ Use first when LinkedIn activity plus tighter role / company filters matter.
|
|
|
279
279
|
`CURRENT_TITLE` lookups. Seniority filters are supporting constraints, not a
|
|
280
280
|
substitute for target roles. Example: VP Sales / VP Revenue / Head of Growth
|
|
281
281
|
should use title filters, not only `SENIORITY_LEVEL: Vice President`.
|
|
282
|
+
- When a title lookup returns multiple options, choose the option that most
|
|
283
|
+
closely matches the intended role, not the first option by position. If
|
|
284
|
+
`Head of Growth` appears after `Head of Marketing`, use `Head of Growth`.
|
|
282
285
|
- For reply-likelihood-first outbound, Sales Nav is the second choice after Signals: use it when the TAM is not active enough on LinkedIn, when Signals cannot sustain enough good fits, or when the targeting thesis depends on tighter role/company control than Signals can provide.
|
|
283
286
|
- For InMail or LinkedIn-send motions, establish the baseline TAM first, then test a `POSTED_ON_LINKEDIN` slice when the pool can still sustain a campaign.
|
|
284
287
|
- Treat recent posters as a preferred first-send slice, not just a nice-to-have proxy. When the recently-posted slice still yields enough projected good fits, prefer it because reply / acceptance performance is usually materially better than the cold full-TAM pool.
|
|
@@ -57,6 +57,12 @@ Example search name: "Active CXOs at 201-500 companies"
|
|
|
57
57
|
business development, partnerships, marketing, operations, and other noisy
|
|
58
58
|
roles.
|
|
59
59
|
|
|
60
|
+
Do not blindly use the first `lookup_sales_nav_filter` result. Review the
|
|
61
|
+
returned options and choose the closest semantic title match. If the first
|
|
62
|
+
result for "Head of Growth" is "Head of Marketing" but a later option is
|
|
63
|
+
"Head of Growth", use "Head of Growth". If no close title match exists,
|
|
64
|
+
retry with a tighter title query or omit that role and call out the tradeoff.
|
|
65
|
+
|
|
60
66
|
Dynamic filters (REQUIRE lookup):
|
|
61
67
|
|
|
62
68
|
- REGION: "United States", "California", "London"
|