Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

Creator Tools Find Creator Emails

social_find_creator_emails
Read-only

Accepts a supported platform and creator handle, using the same verified social-profile discovery flow as Find Social Profiles. Supported starting platforms are Instagram, TikTok, YouTube, X/Twitter, and Facebook. A leading @ is optional; YouTube also accepts channel IDs. Scans publicly listed profile bios and contact links, recognized link-in-bio pages, and a bounded set of creator-declared public website pages. Other accounts are scanned only when explicitly linked or verified through reciprocal profile links or shared owner-controlled websites. Returns deduplicated email addresses with available public source URLs and source types. URLs from internal-only sources are omitted from email provenance and scan diagnostics; an email found only through those sources has an empty sources array. Partial and limited-scan flags still reflect the complete scan. Addresses may belong to the creator, their management, or a booking contact; the endpoint does not guess addresses or verify mailbox deliverability. Login-only contact details and private account data are not accessed. A successful lookup with no publicly listed email returns an empty emails array. Optional failed or timed-out scans are reported with partial results and diagnostics, so an empty partial result is not proof that no address exists. Successful live lookups cost 1 credit when emails is empty, including successful partial empty results, and 10 credits when any email is returned. Cache hits cost 0 credits. Missing or invalid inputs, missing source profiles, and failed lookups cost 0 credits. Multi-source discovery can take several seconds and may time out; retry failed requests rather than treating them as no-email results. Contact fields come from public creator pages. To request removal of your own information from Scrape Creators results, email support@scrapecreators.com with the profile URL. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. Creator Tools Find Creator Emails API View Pricing Find public creator emails. Live: 1 credit with no emails, 10 credits with any email. Cache hits/failures: 0 credits. Empty or partial results do not prove no email exists. 1 credit with no emails; 10 credits with any email (live lookups) Accepts a supported platform and creator handle, using the same verified social-profile discovery flow as Find Social Profiles. Supported starting platforms are Instagram, TikTok, YouTube, X/Twitter, and Facebook. A leading @ is optional; YouTube also accepts channel IDs. Scans publicly listed profile bios and contact links, recognized link-in-bio pages, and a bounded set of creator-declared public website pages. Other accounts are scanned only when explicitly linked or verified through reciprocal profile links or shared owner-controlled websites. Returns deduplicated email addresses with available public source URLs and source types. URLs from internal-only sources are omitted from email provenance and scan diagnostics; an email found only through those sources has an empty sources array. Partial and limited-scan flags still reflect the complete scan. Addresses may belong to the creator, their management, or a booking contact; the endpoint does not guess addresses or verify mailbox deliverability. Login-only contact details and private account data are not accessed. A successful lookup with no publicly listed email returns an empty emails array. Optional failed or timed-out scans are reported with partial results and diagnostics, so an empty partial result is not proof that no address exists. Successful live lookups cost 1 credit when emails is empty, including successful partial empty results, and 10 credits when any email is returned. Cache hits cost 0 credits. Missing or invalid inputs, missing source profiles, and failed lookups cost 0 credits. Multi-source discovery can take several seconds and may time out; retry failed requests rather than treating them as no-email results. Contact fields come from public creator pages. To request removal of your own information from Scrape Creators results, email support@scrapecreators.com with the profile URL. If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit with no emails; 10 credits with any email (live lookups)). See the Caching page for details. Live 1 credit if no emails, 10 if any email; cache hits and failures 0. Empty or partial results do not establish that no email exists.

Input Schema

NameRequiredDescriptionDefault
handleYesCreator handle without a profile URL. A leading @ is optional.
platformYesSource social platform
cache_max_ageNoIf we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit with no emails; 10 credits with any email (live lookups)). [See the Caching page for details.](https://docs.scrapecreators.com/caching)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag readOnly, openWorld and non-destructive, and the description adds substantial context beyond them: no login-only or private data is accessed, addresses are not guessed or deliverability-verified, provenance URLs from internal-only sources are omitted leaving an empty sources array, and multi-source discovery can take several seconds and time out. It also discloses the full credit model (1 credit empty, 10 with an email, 0 for cache hits and failures), which an agent spending on a user's behalf needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences are well front-loaded, but the body repeats the entire ~250-word paragraph verbatim, restates the pricing rule three separate times, and mixes in unrelated Nexscope boilerplate and a data-removal support address. The 'at least 10 Nexscope credits' line also sits uneasily against the 1-credit/10-credit model stated elsewhere, forcing the agent to reconcile duplicated, partly conflicting cost text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter lookup with no output schema, the description covers what an agent needs: result shape (deduplicated emails with source URLs and types), empty-vs-partial semantics, provenance caveats, latency and retry behavior, and cost. The deduction is for the internal cost inconsistency and duplicated boilerplate, which reduce confidence rather than fill a genuine gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description contributes real meaning the schema lacks: which platforms are valid starting points, that a leading @ is optional, and that YouTube additionally accepts channel IDs (the handle field's schema text does not mention channel IDs). It adds nothing further about cache_max_age beyond what the schema already spells out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and resource ('find creator emails' from a platform + handle) and scopes the scan surface (bios, contact links, link-in-bio pages, bounded public site pages). It also positions itself against the named sibling 'Find Social Profiles' as the email-extraction counterpart to that discovery flow. What it never states is why an agent would pick it over contact-adjacent siblings like social_linkbio or social_linktree, so the differentiation is indirect rather than crisp.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: use it to get publicly listed contact addresses for a known creator on five named platforms. It adds genuinely useful operational guidance — retry timed-out requests rather than treating them as no-email results, and don't read an empty partial result as proof of absence. It stops short of explicit when-not/alternative routing (e.g., use Find Social Profiles when you want the profile itself, or linkbio tools when you only need the bio page).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources