Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Calendly, HubSpot & Chili Piper Sales Funnel Spy

detect_b2b_sales_funnel_calendly_hubspot
Read-onlyIdempotent

Detect Calendly, Chili Piper, HubSpot Meetings, Intercom, Drift, and high-intent B2B demo booking funnels across target company domains to identify sales-ready prospects.

Instructions

Detect Calendly, Chili Piper, HubSpot Meetings, Intercom, Drift, and high-intent B2B demo booking funnels across company websites ($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": {
      "domains": "<domains>"
    },
    "name": "detect_b2b_sales_funnel_calendly_hubspot"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesTarget B2B domains

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, openWorldHint and destructiveHint false, so safety is covered. The description adds genuinely useful behavioral context in the form of a pricing rate ($0.80/1k), but it says nothing about what a detection result contains (which vendors matched, evidence, confidence), so it goes only modestly beyond the structured fields.

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?

One sentence, front-loaded with the detected technologies and ending on cost. The vendor list is long but each name is load-bearing for fingerprinting recognition; nothing is redundant filler.

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 should convey what comes back, and it does not — an agent cannot tell if it receives per-domain boolean flags, matched script URLs, or a score. Given the tool's simplicity (one array parameter) and annotation coverage this is adequate, but the missing result shape is a real gap.

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?

There is a single parameter with 100% schema description coverage ("Target B2B domains"). The description adds no constraints such as domain format, batch limits, or whether subdomains are accepted, so the schema carries the semantics and the baseline of 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?

The description pairs a specific verb ("Detect") with a concrete resource (Calendly, Chili Piper, HubSpot Meetings, Intercom, Drift booking funnels) and scopes it to "company websites." An agent can tell this is a technology-fingerprinting tool rather than a CRO audit or ad-pixel detector, though it never explicitly names the neighboring options.

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 named alternative. The phrase "high-intent B2B demo booking funnels" hints at a prospecting scenario, but the agent must infer on its own whether to reach for this versus analyze_landing_page_cro_funnel or detect_ad_spend_pixels.

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