Skip to main content
Glama

TrueScrape

by io.github.TrueScrape
OverviewDiscussionsAdmin

identity: Find a creator's other social profiles

identity_findSocialProfiles
Read-only

Find a creator's other social profiles. Starts from one public profile and reports the other accounts that profile can be shown to own: profiles it links to directly, profiles reached through a recognised link-in-bio page (Linktree, Komi, Pillar, Lnk.Bio, LinkMe), and same-handle accounts on the other supported platforms that link back to the source or share a website only the owner controls. Covers Instagram, TikTok, YouTube, X and Facebook. A same-handle account with no corroboration is reported under candidates, never as a profile: the handle matching is a fact handed over, not a claim. There is no search-engine discovery and no display-name matching; neither is evidence of ownership. Every result carries the evidence type it rests on. Each entry in failures carries the inner error’s code and message, so "we checked and found nothing" (upstream_not_found, empty_result) stays distinguishable from "we could not check" (upstream_blocked, not_configured); only the second kind sets partial. Not covered: any platform outside the five, and links a creator has not published. An X/Twitter source can only be resolved by same-handle probing, because X exposes no bio links at all to a logged-out caller. The 20-second budget stops the composite scheduling new inner fetches; it does not abort one already in flight, so a slow leg is reported as a timeout while its request finishes unread. Link-in-bio expansion is verified against fixtures only, because no channel sampled live from our network published a link-in-bio URL to expand. A partial: true answer is cached for the same seven days as a complete one, so pass cache_max_age=0 to refetch after a transient block rather than being served the gap for a week. Pricing is per source checked: the 10 credits buy the legs this call runs (the starting profile, each link-in-bio page expanded, and each same-handle probe), and a leg listed in unchecked is not charged for, so a partial answer costs ceil(10 x legs answered / legs attempted) and never more than 10. Any response with an empty profiles AND an empty candidates costs nothing at all, whatever unchecked says: an answer carrying no account has delivered nothing to charge for, and the unchecked disclosure ships free. When every leg was checked and none carries another account that free answer is an empty_result; when nothing beyond the starting profile could be checked it is an error, because "no other accounts" would then be a fact we did not establish. Costs 10 credits.

Input Schema

NameRequiredDescriptionDefault
handleYesBare handle (@nasa). YouTube also accepts a UC… channel id. URLs are rejected.
platformYesPlatform the handle belongs to. `x` is an alias for `twitter`.
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only mark read-only and open-world, while the description adds substantial behavior: corroboration rules, candidate versus profile distinction, failure code taxonomy, partial semantics, timeout behavior, caching of partial results, and detailed credit pricing. This is rich transparency well beyond the annotations.

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

Conciseness3/5

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

The core purpose is front-loaded, but the definition is very long and mixes invocation guidance with internal fixture-verification caveats and an elaborate pricing formula. Much of it is relevant, yet the volume and some QA detail reduce conciseness.

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

Completeness5/5

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

With no output schema, the description still explains the meaningful return concepts: profiles, candidates, failures, partial, and unchecked, plus how errors distinguish not-found from blocked. Given the tool's complexity, this is complete enough for correct invocation and interpretation.

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?

The schema documents handle and platform well, but cache_max_age has no schema description. The description compensates by explaining that cache_max_age=0 refetches after a transient block despite seven-day partial caching, adding meaning for the undocumented optional parameter.

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 description states a specific verb and resource: find a creator's other social profiles starting from one public profile, with supported platforms and evidence types. It is clear, but it does not explicitly name the platform-specific profile or link-in-bio sibling tools it differs from, so sibling differentiation is left implicit.

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?

It gives clear context: use when starting from a handle on one of five platforms and needing corroborated cross-platform accounts, and it states exclusions such as no search-engine discovery, no display-name matching, and no platforms outside the five. It does not name alternative sibling tools such as linktree_page or instagram_profile, so alternatives are not explicit.

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

All TrueScrape 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