Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

B2B Competitor Case Study & Customer Logo Extractor

extract_b2b_case_studies_logos
Read-onlyIdempotent

Extract named enterprise customers, case study URLs, client logo walls, and testimonial quotes from competitor B2B domains to map customer proof and prioritize outbound targets.

Instructions

Extract named enterprise customers, case study URLs, client logo walls, and testimonial quotes from competitor B2B 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": "extract_b2b_case_studies_logos"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesCompetitor B2B company domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds only a cost signal ($0.80/1k), which is genuinely useful for a paid open-world crawler, but says nothing about crawl scope (homepage vs. subpages), depth, volume of results per domain, or whether sites can be blocked -- real behavioral questions for this tool.

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 front-loaded sentence that pairs the extracted artifacts with the target and the price. Nothing is padded or repeated from the title.

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 no output schema, the description usefully enumerates the four return categories, which is the main thing an agent needs to judge relevance. It stops short of covering crawl scope or result volume per domain, the remaining gap for a one-parameter, open-world 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 coverage is 100% with a single required array parameter, so the baseline is 3. The description's "competitor B2B websites" loosely reinforces what a domain means here, but adds no format, batching, or limit guidance beyond the schema.

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?

Specific verb ("Extract") plus a precise, enumerated set of resources (named enterprise customers, case study URLs, logo walls, testimonial quotes) and a stated target (competitor B2B websites). The output categories alone distinguish it from siblings like extract_saas_competitor_pricing_matrix or build_360_b2b_company_dossier, which harvest different artifacts.

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 only implied: the phrase "from competitor B2B websites" signals a competitive-research context, and the required domains array frames the input as a list of competitor sites. There is no explicit when-to-use, when-not-to-use, or named alternative for adjacent jobs such as pricing extraction or full company dossiers.

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