Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Substack Newsletter & Creator Sponsor Lead Scraper

scrape_substack_newsletter_authors
Read-onlyIdempotent

Extract Substack newsletter metadata, author profiles, posting cadence, subscriber signals, and sponsorship contacts from publication handles or URLs for outreach and lead research.

Instructions

Extract Substack newsletter metadata, author profiles, recent post cadence, subscriber signals, and sponsorship contact links ($0.50/1k).

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": {
      "publications": "<publications>"
    },
    "name": "scrape_substack_newsletter_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicationsYesSubstack handles or URLs, e.g. ["lennysnewsletter", "pragmaticengineer"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral fact not in the annotations: the cost model of $0.50 per 1k records. However, it says nothing about rate limits, batch size limits per call, failure behavior on invalid handles, or how long extraction takes for large publication lists.

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?

It is a single front-loaded sentence that enumerates the extracted fields compactly and appends the pricing signal without padding. Nothing is wasted, though the trailing price parenthetical slightly interrupts the output enumeration.

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 one required parameter, no output schema, and full annotation coverage, the main remaining gap is what comes back per publication. The description partially addresses that by listing the data categories returned (metadata, author profiles, cadence, subscriber signals, contact links). It would be stronger with a note on whether results are one record per publication or per author.

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% and the single `publications` array is fully documented in the schema with concrete example handles. The description adds no syntax, format, or limit constraints (e.g., max array size, handle vs. full URL handling) beyond what the schema already states. Baseline 3 applies when the schema carries the parameter burden.

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 uses a specific verb ('Extract') against a named resource (Substack newsletter metadata, author profiles, post cadence, subscriber signals, sponsorship contacts). The platform specificity (Substack creators/newsletters) separates it from the sibling scrapers targeting other sources such as Apollo, G2, or Shopify. It stops short of explicitly contrasting a named alternative, but the scope is unambiguous.

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, no stated prerequisites, and no mention of alternative tools for adjacent lead-source needs. The only implied usage cue is the platform name itself. An agent must infer the selection conditions from the title alone.

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