Skip to main content
Glama
Substack, B2B Churn & Lead MCP Server

Substack, B2B Churn & Lead MCP Server

by willowswt

find_company_website_contacts

Read-onlyIdempotent

Crawl a company website and its contact and about pages to extract clean emails, phone numbers, social profiles, and company metadata for B2B lead research and outreach.

Instructions

Crawl a B2B company website or domain (url, plus /contact and /about pages) to extract clean contact emails, phone numbers, LinkedIn/X/GitHub profiles, and company metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "find_company_website_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCompany website URL or domain (e.g. 'stripe.com' or 'https://linear.app').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety and network profile is covered. The description adds genuine scope detail beyond that: which paths are fetched (`/contact`, `/about`) and which entity types come back. It stops short of disclosing crawl cost, depth/limits, or behavior on JS-heavy or blocked sites, which would be the remaining high-value behavioral facts.

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

Conciseness5/5

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

A single sentence that front-loads the verb and resource, then closes with the concrete deliverables. No filler, no restatement of the title, and the parenthetical path detail is placed inline where it is immediately useful.

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 one-parameter read-only crawl tool with no output schema, the description covers input shape, crawl scope, and the categories of extracted data, and the four annotations carry the safety/network profile. Minor gap: it does not say whether results are a structured record versus raw scraped text, which matters on domains with no contact page.

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 coverage is 100% and the single `url` parameter is fully documented with both an example domain and a full URL form. The description's mention of appended `/contact` and `/about` pages clarifies behavior rather than parameter syntax, so it adds little meaning the schema does not already convey. Baseline 3 applies.

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?

States a specific verb ('Crawl') against a specific resource ('B2B company website or domain') and enumerates the outputs (emails, phones, LinkedIn/X/GitHub profiles, company metadata). This is clearly distinguishable from the sibling tools by resource domain, though the description never explicitly names an alternative to contrast against.

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 the resource: 'B2B company website' tells the agent this is for outbound/sales contact discovery on a known company domain. However, there is no explicit when-to-use framing, no statement of when NOT to use it, and no routing to siblings like extract_bio_link_emails for non-company sources.

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