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

Substack, B2B Churn & Lead MCP Server

by willowswt

extract_bio_link_emails

Read-onlyIdempotent

Crawl Linktree, Beacons, Carrd, or creator bio URLs to extract verified emails, booking links, socials, and linked storefront domains for lead contact discovery.

Instructions

Crawl a Linktree, Beacons, Stan Store, Carrd, or creator bio URL (url) and extract verified email addresses, Calendly/Cal.com booking links, social accounts, and linked external company/storefront domains.

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": "extract_bio_link_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCreator bio hub URL (e.g. 'https://linktr.ee/...').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 profile is covered. The description adds the categories of data extracted, but it does not disclose rate limits, authentication requirements, public-only constraints, or what "verified" means in practice.

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?

The definition is a single front-loaded sentence with no filler; it moves directly from the crawl target to the extracted result categories.

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 simple one-parameter tool with no output schema, the description adequately states the input type and the categories of returned data. It is slightly incomplete about operational limits and return-format details.

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%, so the schema already defines the sole `url` parameter and gives an example. The description adds value by listing additional supported platforms beyond the Linktree example, but it does not add format or validation details.

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 states a specific verb ("Crawl") and resource ("Linktree, Beacons, Stan Store, Carrd, or creator bio URL") and names the extracted outputs, making it clearly distinguishable from contact-mining and search siblings.

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?

Supported URL types imply when to use it, but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative tool for non-bio URLs.

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