Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Apollo Alternative — B2B Lead, Email & Executive Finder

scrape_apollo_alternative_leads
Read-onlyIdempotent

Discover B2B companies by niche and city, or enrich known domains with verified emails, executive contacts, LinkedIn URLs, phones, deliverability checks, and tech stack signals.

Instructions

Cookie-free Apollo.io alternative: discover B2B companies by niche/city or enrich domains with verified emails, MX/SPF/DMARC status, executive names, LinkedIn URLs, phones, and 35+ tech stack signals ($0.80/1k).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrape_apollo_alternative_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsNoOptional direct company domains to enrich, e.g. ["linear.app", "cal.com"]
queriesNoTarget B2B niche + city queries, e.g. ["B2B SaaS Austin", "RevOps agency New York"]
maxLeadsNoMaximum leads to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and network behavior are covered. The description adds genuinely useful context beyond them — cookie-free sourcing, the per-record price ($0.80/1k), and the verification payload (MX/SPF/DMARC, exec names, phones, tech stack). That said, it does not state whether both inputs can be combined or what happens when no input is supplied.

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 dense sentence that front-loads the positioning ('Cookie-free Apollo.io alternative') before the capabilities. The feature list is long but every clause maps to a real output or constraint, with only the trailing price tag bordering on promotional padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does carry return-value information, which it does well. The notable gap is that all three parameters are optional and the description never explains the default no-argument behavior or whether the two input modes are exclusive, which matters for correct invocation.

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 each of the three parameters is already documented with examples. The description adds no additional syntax, formatting, or interaction semantics (e.g. whether domains and queries merge into one result set) beyond what the schema states, so the 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?

Names a specific verb pair (discover companies by niche/city, or enrich domains) plus a concrete resource and a long list of returned data. It reads clearly as a B2B lead-finder/enricher, but it never names a sibling such as enrich_b2b_company_domain to differentiate the overlap.

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?

The two operating modes are visible by implication from the description ('discover B2B companies by niche/city or enrich domains'), so an agent can infer which parameter path to take. However there is no explicit when-to-use/when-not-to-use guidance and no named alternative for the domain-enrichment case.

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