B2BLeads MCP Server

search_leads

Find real-time B2B companies and business contacts by industry, city, and filters. Returns ready-to-use leads with names, addresses, phones, websites, and emails for sales outreach and research.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text search query, e.g. "construction companies in Munich". Optional if industry+city are given.
`city`	No	City or region to search in, e.g. "Berlin" or "Austin, TX".
`lang`	No	Result language as a BCP-47 tag, e.g. "en" or "pt-BR".
`limit`	No	Max number of results to return (1-20). Defaults to a server-side value if omitted.
`list_id`	No	Existing saved-list ID to append results to.
`rank_by`	No	How to sort results.
`industry`	No	Industry filter. One of the predefined categories.
`open_now`	No	Only return businesses that are currently open.
`list_name`	No	Name of a saved list to find-or-create and append results to.
`radius_km`	No	Search radius in kilometers around the city center.
`min_rating`	No	Minimum rating (0-5) a business must have to be included.
`page_token`	No	Pagination token returned by a previous call, to fetch the next page of results.
`has_website`	No	Only return businesses that have a website.
`price_level`	No	Filter by price level.
`save_to_list`	No	If true, also save the results into a B2BLeads saved list (requires list_id or list_name).
`verified_only`	No	Only return businesses with a verified listing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 24, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses that results are real-time, that email is 'where available,' and that the output is a ready-to-use lead list. However, it does not mention pagination behavior or the side effect that save_to_list can persist results into a saved list, which is relevant given the parameters.

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?

Two sentences with no filler. The core action and output are front-loaded, and the usage guidance is a separate, efficient sentence. Every clause earns its place.

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 tool with 16 optional parameters and no output schema, the description does a solid job of explaining the output shape and the intended use case. The schema covers parameter semantics, and the description covers the high-level outcome. It is slightly incomplete in not addressing pagination or saved-list side effects, but overall it is sufficient for an agent to invoke the tool correctly.

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%, so the baseline is 3 and the schema already documents every parameter. The description adds no extra parameter-level meaning beyond naming 'industry, city, and other filters,' which is acceptable but not additive.

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?

The description uses a specific verb ('Search') plus a clear resource ('companies and business contacts') and scoping filters ('by industry, city, and other filters'). It also names the concrete output ('ready-to-use list of leads') with field details, making it easy to distinguish from the sibling list_industries tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'whenever the user asks to find, list, or collect businesses/companies for sales, outreach, or research.' It provides clear context but does not mention exclusions or contrast with the sibling list_industries tool, so it loses one point.

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

Deploy Server

search_leads

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools