Skip to main content
Glama
mambalabsdev

mcp-creator-profile-reader

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_influencer_profilesA

Reads creator profiles on TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts from handles or profile URLs. Returns one flat row per creator with display name, follower count, following count, post count, engagement rate, verified flag, bio text, bio link, any public business email, a country guess with the method behind it, and a stable creator_id. Engagement rate is lifetime likes per post over followers, and the method is named on the row rather than implied. It reads profiles only: it does not follow the bio link, which is what Link in Bio Scraper and Newsletter Detector does. Every row carries row_status and error_reason. Charges $0.001 per run plus $0.006 per profile read, 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; contribute_to_shared_pool is on by default and turning it off leaves the run reading the pool and writing nothing. Only public data already in the returned rows is contributed, nothing from your Apify account or your input, and a contribution is not charged. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly defined and distinct.

Naming Consistency5/5

The tool name follows a clear verb_noun pattern in snake_case, consistent with common MCP conventions. There are no other tools to create inconsistency.

Tool Count4/5

A single tool is slightly below the typical 3-15 range, but it perfectly matches the server's narrow purpose of reading creator profiles. The tool is comprehensive within its scope, so the count feels appropriate rather than insufficient.

Completeness5/5

The tool covers all major creator platforms (TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, podcasts) and returns extensive profile data. It clearly scopes out bio-link following, which is explicitly handled by other servers, so there are no obvious gaps in the stated profile-reading domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues