Skip to main content
Glama

Enterprise B2B Lead, Tech Stack & Regulatory Signal MCP

List Bulk B2B Lead Scrapers

list_bulk_b2b_scrapers
Read-onlyIdempotent

Lists pay-per-result cloud scrapers for exporting 100 to 50,000+ verified B2B leads (NetSuite ISVs, SEC Form D startups, YC batches, Shopify stores, Workday/ATS jobs).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bulk_b2b_scrapers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoOptional filter: erp, funding, hiring, ecommerce, marketing, enrichment, or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond the annotations: the scrapers are pay-per-result, cloud-hosted, and targeted at ranges of 100 to 50,000+ verified leads. It does not describe the result fields, cost specifics, or whether listings are paginated.

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?

A single front-loaded sentence with no filler: verb, resource, pricing model, scale, and coverage all appear immediately. The parenthetical exemplar list is dense but each item earns its place by signalling the supported niches.

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 zero-required-parameter read-only listing tool this covers what it lists and at what scale, which is the core need. Two gaps remain relevant to correct invocation: what a returned scraper record contains, and whether results are paginated or filtered server-side by the niche parameter.

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% and the schema itself documents the single optional 'niche' filter with its allowed values, so the schema does the heavy lifting. The description's niche examples (NetSuite, YC, Shopify, Workday) do not map to the enum values (erp, funding, hiring, ecommerce, marketing, enrichment), so it adds no filtering guidance beyond what the schema already states.

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?

States a specific verb and resource: lists pay-per-result cloud scrapers for bulk B2B lead export. The parenthetical catalog of niches (NetSuite ISVs, SEC Form D startups, YC batches, Shopify stores, Workday/ATS jobs) makes the resource concrete. It does not explicitly contrast with the sibling tools, which perform actions on leads rather than listing scraper 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?

Provides no when-to-use or when-not guidance and names no alternative. The phrase 'for exporting 100 to 50,000+ verified B2B leads' hints at the scenario, but the agent must infer that this is a discovery/catalog step preceding a scrape rather than an extraction call itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.