Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Clutch.co B2B Agency Leads, Ratings & Verified Emails

scrape_clutch_b2b_agency_leads
Read-onlyIdempotent

Extract B2B agency leads from Clutch.co by service and city, including verified ratings, domains, emails, phones, booking funnels, and LinkedIn URLs for outbound prospecting.

Instructions

Extract B2B marketing, SEO, web design & software agencies from Clutch.co profiles with verified ratings, official domains, emails, phones, booking funnels, and LinkedIn URLs ($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_clutch_b2b_agency_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesAgency service + city queries, e.g. ["SEO agency Austin", "PPC agency Miami"]
maxAgenciesNoMaximum agency leads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful output-field context (ratings, domains, emails, phones, booking funnels, LinkedIn URLs) and pricing ($0.80/1k), but it omits rate limits, data freshness, and whether all fields are returned for every lead.

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?

The description is a single front-loaded sentence with no filler. It compactly communicates source, extracted fields, and cost in an appropriately sized form.

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?

For a two-parameter scraper, the description plus annotations covers source, outputs, cost, and safety. However, because there is no output schema, it does not clarify result structure or whether maxAgencies applies per query or across all queries, leaving practical gaps.

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 the schema documents both parameters with examples and a default. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb, 'Extract', and a specific resource: B2B marketing, SEO, web design & software agencies from Clutch.co profiles. The named source and agency focus clearly distinguish it from sibling scrapers such as Google Maps leads or Apollo alternatives.

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?

The description does not explicitly say when to use this tool versus alternatives, nor does it name exclusions or prerequisites. Usage is only implied by the tool's purpose, leaving the agent without routing guidance among lead-scraping siblings.

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