Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Cold Email Personalized Icebreaker Generator

generate_cold_email_icebreakers
Read-onlyIdempotent

Crawls prospect websites to create personalized B2B cold-email icebreakers, value-prop summaries, and outreach hooks from submitted domains.

Instructions

Crawl prospect websites and generate personalized B2B cold email first-line icebreakers, value-prop summaries, and Clay/Instantly/Smartlead outreach hooks ($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": {
      "domains": "<domains>"
    },
    "name": "generate_cold_email_icebreakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesProspect domains, e.g. ["vercel.com", "supabase.com"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.1/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, so the safety profile is covered; the description contributes the non-obvious cost signal ($0.50/1k) and confirms live crawling of external sites, which matters for spend planning on batch runs. It stops short of describing per-domain failure behavior or whether one hook or many are returned per domain.

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?

A single dense sentence with the core action and deliverables front-loaded and the pricing tucked at the end. No filler, no restatement of the title.

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 must convey return shape; it lists the artifact types but not format, count per domain, or whether domains are processed in one batch. For a scraping-plus-generation tool with variable cost, a sentence on per-domain results or failures would close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes an example array, so the schema carries the syntax burden. The description adds the meaningful semantics—that these domains are prospect websites that will be crawled, linking input directly to the output artifacts—which goes slightly beyond 'Prospect domains.'

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?

Names two specific verbs (crawl, generate) plus the exact artifacts produced: first-line icebreakers, value-prop summaries, and outreach hooks for named platforms (Clay/Instantly/Smartlead). No sibling tool in the catalog produces cold-email copy from domains, so an agent can distinguish it immediately.

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 phrasing 'B2B cold email' implies the outreach-prospecting context, but there is no explicit when-to-use statement, no prerequisites (e.g., that domains must be live public sites), and no named alternative when the agent wants company data rather than copy—despite many sibling tools operating on the same domains.

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