Skip to main content
Glama
mambalabsdev

@mambalabsdev/mcp-link-in-bio-newsletter-checker

Official

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
check_link_in_bio_and_newsletterA

Follows the link in bio page behind a creator handle, or a link in bio URL you already hold, and reports whether the creator runs a newsletter, which email platform hosts it, and the page URL that proves it. Also returns the link in bio host, the creator's own website resolved through any redirect, every outbound link found, the public business email, a manager or booking email with the page it came from, a matched talent agency name and domain, and what the creator sells: course, coaching, digital product, merch, membership, brand deals, and discount codes. Every row carries newsletter_check_method, row_status, and error_reason, so a no is told apart from an unknown. Charges $0.002 per run plus $0.008 per creator checked, and on top of that $0.004 per headless browser render, $0.005 per website email scan, $0.003 per agency match, and $0.01 per Instagram bio fetch, each only when that step runs. Every paid step is its own switch (render_unreadable_pages, scan_website_for_email, match_agencies, escalate_on_block, ai_check), so a call runs only the checks you turn on, and max_residential_reads caps the residential Instagram reads. The AI check uses your own Anthropic or OpenAI key and is billed by them, not here. 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.1/5.0

Scored across 1 tool

Disambiguation4/5

With only a single tool there is no risk of an agent confusing it with a sibling, so misselection is impossible. However, the one tool internally bundles many distinct capabilities (newsletter detection, email scanning, agency matching, Instagram bio fetch, AI check), so its 'purpose' is broad rather than crisply singular.

Naming Consistency5/5

There is only one tool, named check_link_in_bio_and_newsletter in a clear verb_noun snake_case style that matches its action. No competing conventions exist to create inconsistency.

Tool Count2/5

A single monolithic tool exposes an enormous parameter surface (five paid-step switches, max_residential_reads, model keys, pool contribution) that would be far more usable split into focused tools. One tool for this breadth of behavior falls in the 'too few' band.

Completeness4/5

The actor is explicitly read-only and covers its stated domain thoroughly: newsletter status, host platform, proof URL, outbound links, emails, agency match, and commerce signals, each with row_status and error_reason. The main gap is the absence of any batch or multi-handle entry point, which an agent must work around by calling repeatedly.

Maintenance

ActivityMaintained
ResponsivenessNo issues