Skip to main content
Glama
mambalabsdev

Prospect Engine MCP Server

by mambalabsdev

Run Prospect Engine

run_prospect_engine
Read-onlyIdempotent

Enrich companies, discover job postings, find contacts, or run a full ICP-gated outreach workflow for B2B lead generation.

Instructions

A composed prospecting actor with four modes. enrich_companies resolves identity, firmographics, LinkedIn and social for each domain or company name you supply, and needs no vendor key at all. discover_jobs finds who is hiring for your keywords and resolves the real employer behind each posting, including postings a job board placed on an employer's behalf. find_contacts finds people at the companies you name, with optional email discovery and verification. full runs discovery, enrichment, ICP scoring and then contact discovery, passing only the companies at or above min_icp_score through to the contact stage. Every row comes back flat and Clay ready with per field provenance. Vendor keys are yours: you supply them, those vendors bill you directly, and the per event price covers the actor only. discover_jobs and full require a SerpApi key, which is a different vendor from the Serper key that powers people search. Note that this actor is a pass through wrapper over the live actor, so any classification behavior you see is the actor's own. Requires an APIFY_TOKEN and consumes Apify credits. Read only: it enriches and discovers, it writes nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoWhat to run. enrich_companies resolves identity, firmographics, LinkedIn and social for each company. discover_jobs finds who is hiring for your keywords and resolves the real employer from the job description. find_contacts finds people at each company. full chains all three. Default: "enrich_companies".
countryNoTwo letter country code for job search, for example us or gb. Default: "us".
domainsNoOne domain per line. Used by enrich_companies and find_contacts.
keywordsNoRoles to search for. Used by discover_jobs and full. Example: copy editor, proofreader, content editor. Default: ["copy editor", "proofreader", "content editor"].
locationNoOptional location filter for job search, for example New York.
max_pagesNo1 to 5. Each page is one SerpAPI call, so this is the main cost dial on discovery. Default: "1".
score_icpNotrue to score every row against the ICP rules and tier it A to D. Default: "true".
seniorityNoc_level, vp, director, manager, senior.
icp_presetNoWhich scoring model to apply. "proofed_editorial" scores for a seller of managed copy editing and proofreading. "generic_b2b" scores on hiring intent, employer resolvability and headcount with no service-specific vocabulary. Default: "proofed_editorial".
job_titlesNoTitles to search for when finding contacts.
skip_cacheNotrue to ignore the 7 day cross-run cache and recompute everything. Default: "false".
departmentsNomarketing, sales, engineering, product, finance, hr, operations, legal.
max_resultsNoCap on postings returned per run. Keeps a broad keyword set from running away. Default: "25".
remote_onlyNotrue to keep only postings flagged remote by the board. Default: "false".
serpapi_keyNoYour SerpApi key. Required by discover_jobs and full. Distinct from a Serper key: different vendor.
verify_emailNotrue to verify each address. Needs a Reoon or BounceBan key. Default: "true".
company_namesNoOne name per line. Used when you have a name but no domain.
include_emailNotrue to run the email waterfall. Needs an Icypeas or Prospeo key, which you supply and are billed for directly. Default: "false".
lookback_daysNoDrop postings older than this many days. Sent as a string because Clay sends every field as a string. Default: "30".
min_icp_scoreNoIn full mode, only companies scoring at or above this go on to contact discovery. Default 45: at 25 the filter passed every keyword-discovered editorial posting, because 25 is the floor such a posting can score. Default: "45".
reoon_api_keyNoYour Reoon key. First email verification provider.
include_socialNotrue to resolve Facebook, Instagram, X and YouTube alongside LinkedIn. Default: "true".
serper_api_keyNoYour Serper.dev key. Powers people search in find_contacts, which is the highest-coverage layer. Without it the free fallback is measurably poor.
icypeas_api_keyNoYour Icypeas key. Runs on Findymail misses.
prospeo_api_keyNoYour Prospeo key. Runs on the residual after Findymail and Icypeas.
signal_taxonomyNoOverride the default signal types. Each entry is an object with type, strength, title_keywords, and optional also_keywords and description_keywords.
target_contactsNo1 to 25. Default: "3".
company_size_maxNoDrop companies above this headcount. Same condition as the minimum.
company_size_minNoDrop companies below this headcount. Only takes effect once headcount is known, so it applies in full mode and to any discovery row that carried an employee count. Discovery alone does not enrich.
exclude_staffingNotrue to drop postings from staffing and recruitment agencies. Default: "true".
bounceban_api_keyNoYour BounceBan key. Second verifier, used for the catch-all case.
findymail_api_keyNoYour Findymail key. First provider in the email waterfall.
new_postings_onlyNotrue to return only postings not seen in a previous run. Default: "false".
previous_run_dateNoYYYY-MM-DD watermark for delta detection when the cross-run cache is unavailable.
extra_marketplacesNoAdditional marketplace names to filter out.
fetch_posting_pageNotrue to open the job posting when the description alone does not identify the employer. Slower, and it is what catches a job board posting on an employer's behalf. Default: "true".
extra_exclude_namesNoAny company whose name contains one of these is excluded.
source_timeout_secsNo5 to 120. A source that exceeds this is marked degraded and the run continues. Default: "30".
exclude_marketplacesNotrue to drop Upwork, Fiverr, Freelancer and similar gig listings. Default: "true".
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explicitly states 'Read only: it enriches and discovers, it writes nothing,' reinforcing the annotations. It adds substantial context beyond annotations: vendor key billing, APIFY_TOKEN requirement, pass-through wrapper nature, and that classification behavior is the actor's own. This fully discloses behavioral nuances.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-organized: it starts with the core definition, then breaks down each mode, then covers vendor keys and operational notes. Every sentence contributes unique information (e.g., per-field provenance, SerpApi vs Serper distinction), though some redundancy exists. For a tool with 39 parameters and 4 modes, the length is justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (39 parameters, 4 modes, no output schema), the description is remarkably complete. It covers mode-specific behaviors, key requirements, billing, output format ('Every row comes back flat and Clay ready with per field provenance'), caching, and read-only semantics. It effectively compensates for the lack of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for all 39 parameters, so the baseline is 3. The description adds high-level flow context (e.g., 'full runs discovery, enrichment, ICP scoring and then contact discovery') but does not provide additional details on individual parameters beyond what the schema already specifies. It does not compensate further, so a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'A composed prospecting actor with four modes' and enumerates each mode with its function (enrich_companies, discover_jobs, find_contacts, full). It clearly defines the tool's purpose of enriching and discovering prospects, leaving no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use each mode and what prerequisites are needed (e.g., 'discover_jobs and full require a SerpApi key'). It notes that enrich_companies needs no vendor key and that the tool is read-only and Clay-ready, implying typical use cases. However, there are no explicit exclusions or alternatives since no sibling tools exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-b2b-prospect-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server