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. Requires an APIFY_TOKEN and consumes Apify credits. Read only. |
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 selecting the wrong tool. The tool itself handles multiple modes (discovery, profile read, link check) internally, but these are not separate selectable operations.
The single tool name follows a clear verb_noun pattern: build_influencer_lead_list. With only one tool, there is no inconsistency to evaluate, but the name accurately conveys the action and target.
The server provides exactly one tool, which feels thin for a typical MCP server. Although the single tool is comprehensive and covers the entire lead-list-building pipeline, a 1-2 tool server is borderline per the calibration guidelines.
The tool fully covers the domain of influencer lead list building: discovery by keyword or niche, profile reads, link-in-bio checks, and enrichment with emails, agency matches, and platform data. Options to skip stages provide flexibility, and no obvious operations are missing.