Influencer Lead List 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. Get one at https://console.apify.com/account/integrations |
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_influencer_lead_listA | Runs the three stages of the suite in one call: find creators by keyword or curated niche, read each profile, then follow the link in bio page. Returns one flat row per creator carrying handle, profile URL, display name, follower count, a stable creator_id and the method that produced it, the public business email, a manager email, a matched talent agency, newsletter status and the platform behind it, and what the creator sells. Start from keywords or a niche to discover creators, or hand it handles you already hold to skip discovery. Skipping the link check stops after the profile read. Every row carries row_status and error_reason, and a creator dropped by the country filter says so rather than disappearing. Charges $0.002 per run, then $0.007 per creator found, $0.006 per profile read, and $0.008 per link check, plus $0.004 per headless browser render, $0.005 per website email scan, $0.003 per agency match, and $0.01 per Instagram bio fetch when those steps run. The AI check uses your own Anthropic or OpenAI key and is billed by them. Contributes the public records in its rows to a shared creator pool, free and on by default; |
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
With a single exposed tool there is no internal overlap or risk of misselection. However, the description repeatedly points to companion 'single stage' tools that are not in the set, creating confusion about what is actually callable.
The lone tool uses a clear snake_case verb_noun pattern (build_influencer_lead_list) that matches the server's domain. With only one tool there is no possibility of convention drift.
A single monolithic tool bundles three distinct stages (discovery, profile read, link check) that the description itself admits are cheaper to run individually, yet no per-stage tools are exposed. One tool is too thin for the advertised 'suite' scope.
The surface has clear dead ends: the description references `contribute_to_shared_pool` and single-stage tools that do not exist as callables. There is also no way to inspect run status, retrieve results by run ID, or manage the shared-pool opt-out programmatically.