Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Whatnot & Live Reseller Shop Leads, Ratings & Socials

scrape_whatnot_live_seller_leads
Read-onlyIdempotent

Find Whatnot live auction sellers and collectible, sneaker, and vintage resellers by category, returning profile URLs, storefronts, social handles, and contact emails for B2B lead generation.

Instructions

Discover Whatnot live auction sellers and collectible/sneaker/vintage resellers with profile URLs, categories, external storefronts, social handles, and contact emails ($0.75/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": {
      "categories": "<categories>"
    },
    "name": "scrape_whatnot_live_seller_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoriesYesLive commerce category keywords, e.g. ["pokemon cards", "sneakers", "vintage streetwear"]
maxSellersNoMaximum seller leads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4/5.0
Behavior4/5

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

With annotations already declaring readOnly/openWorld/idempotent/non-destructive, the description adds two genuinely useful facts: the cost model ($0.75 per 1k leads) and the concrete field set that comes back, which matters because there is no output schema. It does not disclose coverage limits, whether emails are always present, freshness/caching of results, or pagination behavior, so it stops short of a 5.

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 with no filler: target segment first, then returned fields, then price. Every clause carries information an agent can act on.

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?

For a two-parameter read tool with no output schema, the description covers the target segment, the returned fields, and the cost. Gaps remain around result guarantees (are emails/socials always populated?), data freshness, and volume limits tied to maxSellers, but nothing blocks 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% and the schema itself supplies keyword examples for 'categories' and a default of 15 for 'maxSellers'. The description adds no semantics beyond what the schema already documents, only the price framing that implies volume-based cost. Baseline 3 is appropriate.

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 ('Discover') and a precisely scoped resource ('Whatnot live auction sellers and collectible/sneaker/vintage resellers'), then enumerates the fields returned (profile URLs, categories, storefronts, socials, emails) so the agent knows exactly what it gets. This clearly separates it from the many other vertical-specific lead scrapers in the sibling list.

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 description tells you this is for live-commerce/reseller lead discovery, so an agent can infer it should be picked when the target segment is Whatnot sellers or collectible/vintage resellers. There is no explicit when-to-use statement, no when-not-to-use, and no reference to alternative lead sources among the many sibling scrapers.

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