Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Skool Community, Creator Emails & Monthly MRR Scraper

scrape_skool_communities_mrr
Read-onlyIdempotent

Scrape Skool.com communities by keyword to extract member counts, monthly subscription prices, estimated MRR, ratings, external links, and creator emails for lead research.

Instructions

Scrape Skool.com communities by keyword: extract member counts, monthly subscription price ($/mo), estimated Monthly Recurring Revenue (MRR), ratings, external links, and creator emails ($0.80/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": {
      "queries": "<queries>"
    },
    "name": "scrape_skool_communities_mrr"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesSkool Discovery keywords, e.g. ["ai agency", "saas founders", "ecommerce"]
maxCommunitiesNoMaximum communities to return
onlyPaidCommunitiesNoReturn only paid recurring communities

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive behavior, so the safety profile is covered. The description adds a genuinely new behavioral fact not present in structured data: creator email extraction is billed at $0.80/1k, which is a cost consideration an agent should surface before invoking. It stops short of describing pagination, rate limits, or what happens when a keyword yields nothing.

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 with verb and resource first, then a colon-delimited output list; the cost parenthetical for creator emails earns its place. Dense but not padded, and nothing is buried after the essential scope statement.

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?

There is no output schema, so the description correctly carries the return-value burden by listing the extracted fields, and the three simple parameters are fully documented in the schema. What remains unstated is scale/cost of the base scrape beyond emails and behavior on empty or rate-limited results, which is a modest gap for a read-only scraper.

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 all three parameters (queries, maxCommunities, onlyPaidCommunities) are self-documented, so baseline 3 applies. The description reinforces the keyword-driven nature of 'queries' and clarifies that MRR is derived from paid subscriptions, but adds no syntax, format, or interaction detail 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?

Names a specific verb and resource (scrape Skool.com communities) qualified by keyword, and enumerates the concrete data returned (member counts, $/mo price, MRR, ratings, links, creator emails). An agent can distinguish this from the sibling scrapers, which target entirely different sources (G2, Clutch, Google Maps, Wellfound). No explicit sibling routing is needed because none of the siblings overlap on data source.

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 through the required 'queries' keyword mechanism and the mention of creator-email extraction, so an agent can infer the discovery use case. There is no statement of when to prefer this over another source or of preconditions/limits, but no sibling competes for the same Skool data, so the omission is low-cost.

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