B2BLeads MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| B2BLEADS_API_KEY | Yes | Your B2BLeads API key. | |
| B2BLEADS_API_URL | No | Override the API base URL. Defaults to https://api.b2bleadsapi.com. | https://api.b2bleadsapi.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_leadsA | Search for companies and business contacts in real time by industry, city, and other filters. Returns a ready-to-use list of leads (name, address, phone, website, rating, and email where available). Use this whenever the user asks to find, list, or collect businesses/companies for sales, outreach, or research. |
| list_industriesA | List the predefined industry categories that can be used as the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one searches for leads, the other provides the valid industry filter values. There is no overlap or potential for misselection.
Both tool names follow a consistent verb_noun pattern (search_leads, list_industries) and are descriptive and predictable.
With only 2 tools, the server covers a minimal but internally coherent scope. It is on the low end of acceptable, but not unreasonably thin given the narrow purpose of lead searching.
The tool set appears to cover the core lead search workflow: filter selection (industries) and the actual search itself. Minor gaps like pagination or detailed lead retrieval are not explicitly mentioned but could be considered average for a simple search-focused server.