Influencer Change Monitor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify token from 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 |
|---|---|
| monitor_influencer_changesA | Rereads a named watchlist of creator handles and compares every field against the state the previous run on that same list name recorded. Returns one row per change with change_type, change_from, change_to, and previous_run_at, alongside the creator handle, profile URL, follower count, newsletter status, bio link, and manager email. The first run on a new list name records the baseline and returns it, so there is something to compare against next time. Each list name keeps its own baseline, so one account can watch a client roster, a prospect list, and a competitor set without them mixing. Turning off the link recheck keeps the pass to profiles only, which is faster and cheaper on a large list. Charges $0.002 per run plus $0.008 per creator rechecked, $0.01 per change found, and $0.01 per Instagram bio fetch when one is needed. Contributes the public records it finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found; |
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 only one tool, there is no possibility of confusing it with another; the purpose is singular and clearly described. An agent cannot misfire between overlapping operations because no overlap exists.
The single tool name follows a clear verb_noun snake_case convention and directly describes the action and object. There are no other names to create inconsistency.
One tool is on the thin side for a server, though the narrow 'monitor' purpose makes it defensible. It is not trivial, but a richer suite might split watchlist management and baseline or change history into separate tools.
The tool covers the full monitoring loop: baseline creation, repeated comparison, multiple named watchlists, and an option to skip expensive rechecks. It does not expose watchlist CRUD or historical change retrieval, but those are minor gaps for a read-only monitor.