Local Business Lead Builder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, required for the server to call the actor. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_local_business_leadsA | Build a local business lead list from the public Google Maps search results. Give queries such as dentist in Austin, TX, or categories plus locations to search every pair. Returns one row per business: name, Google place ID and Maps link, website and domain, phone, full address, latitude and longitude, categories, star rating, review count, and weekly hours, plus one free summary row per search with its counts. Filters for minimum rating, minimum reviews, website, and phone drop businesses before they are billed; a business found by two searches is returned once. Blocked or empty searches come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per business row returned. |
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 1 tool
There is only one tool, so there is no possibility of misselection between competing tools. Its purpose (building a local business lead list from Google Maps queries) is unmistakable from the name and description.
A single snake_case verb_noun-style name (build_local_business_leads) that clearly states the action and the resource. With one tool there is no convention mixing, and the name is descriptive rather than vague.
One tool is defensible because it wraps a single batch workflow (search, filter, and bill in one call), but it is still thin for the domain. There is no separation between starting a run, checking run status, and retrieving results, which forces everything through one opaque operation.
The core operation is richly specified, covering queries, filters, deduplication, output fields, and pricing. However, the description mentions failed runs returned with a run ID yet provides no tool to fetch or retry that run, and there is no way to list prior results or datasets, leaving dead ends.