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

Substack, B2B Churn & Lead MCP Server

by willowswt

search_substack_newsletters_and_authors

Read-onlyIdempotent

Search Substack publications by niche keyword or subdomain, then enrich results with author contacts, sponsor emails, subscriber scale, social profiles, and recent posts.

Instructions

Search Substack publications by niche keyword or subdomain/URL and enrich each newsletter with author name, handle, verified contact/sponsor emails, subscriber scale, bestseller tier, custom domain, sponsorship/media-kit URL, social profiles, and latest 3 published posts.

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": {
      "query": "<query>"
    },
    "name": "search_substack_newsletters_and_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNiche keyword or Substack subdomain (e.g. 'fintech', 'ai agents', 'cybersecurity').
maxResultsNoMax newsletters to enrich (1-15, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety and idempotency (readOnly, openWorld, idempotent, non-destructive), so the bar is lower. The description adds real behavioral value by disclosing exactly what each result is enriched with — verified contact/sponsor emails, subscriber scale, bestseller tier, custom domain, media-kit URL, socials, and latest 3 posts — which tells the agent this is a heavy, per-result enrichment call, not a lightweight listing. It omits latency/cost implications of that enrichment and what happens on zero matches, keeping it out of 5 territory.

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?

A single front-loaded sentence that puts the action and query form first, then the output payload. The long field enumeration is dense but each item is a distinct capability signal rather than filler. Slight cost for reading as a comma-list rather than structured grouping.

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?

With only two parameters, no output schema, and annotations covering the safety profile, the description does the necessary extra work by enumerating the returned enrichment fields. What remains unaddressed is result ordering, behavior when the keyword matches nothing, and the practical cost of enriching many newsletters — minor omissions for a read-only tool of this complexity.

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 both parameters are already documented and the baseline is 3. The description corroborates the query semantics by restating the keyword/subdomain duality and reinforces that maxResults controls how many newsletters get enriched, but adds no format or constraint detail beyond the schema's own 1-15 range note.

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 opens with a specific verb+resource, 'Search Substack publications', and immediately narrows the input surface to 'niche keyword or subdomain/URL'. The enrichment clause makes clear this is not a plain search but a search-plus-contact-enrichment tool, which separates it from generic contact tools in the sibling set. It stops short of explicitly naming an alternative, so it sits at a strong 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no routing against siblings like find_company_website_contacts or extract_bio_link_emails. The phrase 'by niche keyword or subdomain/URL' describes accepted input, not the situation that should trigger this tool. An agent must infer the use case from the name alone.

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