Skip to main content
Glama
subimpact

subimpact-data-mcp

Official
by subimpact
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

website_contacts

Extract emails, phone numbers, and social profile links from a list of websites to build contact and outreach lists without a browser.

Instructions

Website Contact & Social Extractor (Emails, Phones, Socials)

Extract emails, phone numbers and social profile links (Facebook, Instagram, LinkedIn, X, TikTok, YouTube, WhatsApp, Telegram) from any list of websites. Plain HTTP, no browser, respects robots.txt. $0.80 per 1,000 pages scanned, no per-lead fee.

Pricing (pay per event, billed to your Apify account): Page scanned: $0.0008; platform usage billed to your account.

Runs on Apify as subimpact/website-contact-extractor.

Input Schema

NameRequiredDescriptionDefault
maxItemsNoGlobal cap on website rows delivered in one run. The default of 10 keeps a default run under $0.05 at 5 pages per site. Raise it for larger lists. Optional per-page rows are not counted against this cap and are not charged separately.
_maxItemsNoHow many dataset items to return to the model (1-1000, default 50). Truncates the response only; it does not change what the Actor collects or charges for.
startUrlsNoOne entry per website. Full URLs and bare domains are accepted, for example https://apify.com or hartamas.com. The first URL per domain is used as the start page. Duplicate domains are collapsed.
concurrencyNoHow many websites are processed at the same time. Pages within one site are fetched one at a time. Lower this if target sites rate-limit you.
_maxChargeUsdNoPer-run spending cap in USD (default 0.5). Passed to Apify as the run option maxTotalChargeUsd, so the run stops when it reaches this charge.
outputPerPageNoAdds one dataset row per successfully fetched page with that page's own contacts. These page rows are not charged separately. Billing is still per page scanned, charged once after each site row.
maxPagesPerSiteNoPages fetched and scanned per website, including the start page. Links whose URL or anchor text mentions contact, about, team, support, legal, impressum, kontakt or hubungi are fetched first. Higher values find more contacts and cost more page-scanned events.
respectRobotsTxtNoCheck each site's robots.txt before fetching pages and skip disallowed URLs. Keep this on unless you own the sites or have permission to crawl them.
proxyConfigurationNoDirect requests are the default and were measured to work for the example sites. Enable Apify datacenter or residential proxy only if target sites block the Apify IP ranges. A proxy failure fails the request and never falls back to a direct request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden well by disclosing plain HTTP/no browser operation, robots.txt compliance, per-page pricing, no per-lead fee, and Apify billing behavior. It could say more about rate limiting or output structure, but the core behavioral traits are covered.

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 front-loaded, with purpose and extraction targets stated first, followed by technical and pricing details. It is appropriately sized, though the title-like first line and Apify actor attribution are slightly redundant.

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

Completeness4/5

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

For a nine-parameter scraping tool with no output schema and no annotations, the description covers the essential purpose, safety constraint, and billing model. It stops short of describing the output row structure, but the schema compensates for most input semantics.

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%, so the parameters are already well documented. The description adds cost context such as '$0.80 per 1,000 pages scanned' and 'no per-lead fee,' but it does not add parameter-level semantics beyond the schema.

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

Purpose4/5

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

The description states a specific extraction verb and concrete resources: emails, phone numbers, and social profile links from a list of websites. It is clear what the tool does, though it does not explicitly differentiate itself from sibling scraping tools such as web_page_markdown or seo_page_audit.

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

Usage Guidelines3/5

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

Usage is implied by 'from any list of websites' and the robots.txt note, but the description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer its role, but the routing guidance is thin.

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

Deploy Server

Other Tools