Skip to main content
Glama

Viral Outliers

by com.viraloutliers

Search Social Media Profiles

search_profiles
Read-onlyIdempotent

Search tracked social media profiles by handle or name, filtered by platform. Returns profile metadata, follower counts and average performance stats. Use it to resolve a handle to a profile id before fetching stats or posts, or to discover creators in the database. Results may include deactivated profiles (is_active=false), e.g. an account that was renamed or went private, retained with frozen stats; filter on is_active if you only want live accounts. Note a creator who changed handles can appear as two rows (old deactivated + new active). Cost: 1 credit per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryNoHandle, @handle, or profile URL
pageSizeNo
platformsNo

TDQS

A4.5/5.0
Behavior5/5

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

Even with readOnlyHint and idempotentHint annotations, the description adds substantial behavioral details: deactivated profiles are included with frozen stats, duplicate rows for handle changes, and the cost of 1 credit per call. These go 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.

Conciseness5/5

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

The description is four sentences with no fluff. It front-loads the main action, then returns, use cases, edge cases, and cost. Every sentence adds value and the structure is logical.

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?

Given no output schema, the description explains return content (metadata, follower counts, average performance stats). It covers edge cases and cost. Only pagination is implicit, but this does not detract from overall completeness.

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

Parameters3/5

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

Schema coverage is only 25% (only query has a description). The description adds meaning for query ('handle or name') and platforms ('filtered by platform'), but does not explain page/pageSize. With low coverage, it partially compensates but leaves pagination unaddressed.

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

Purpose5/5

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

The description states 'Search tracked social media profiles by handle or name, filtered by platform' with a specific verb and resource. It distinguishes from siblings like get_profile (single profile) and list_tracked_profiles by emphasizing search and handle resolution.

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 explicitly provides use cases: 'resolve a handle to a profile id before fetching stats or posts' and 'discover creators in the database'. It does not name alternatives or explicitly state when not to use, but the context is clear enough.

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

All Viral Outliers toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (search, profile management, post retrieval, async jobs, billing). Some overlap exists among get_trending_outliers, niche_trends, and search_outliers, but their descriptions differentiate free/unauthenticated, niche-specific, and filtered search, so an agent can usually pick correctly.

Naming Consistency4/5

The vast majority of tool names follow a verb_noun pattern (crawl_profile, get_post, remix_post, track_profile). The main exception is 'niche_trends', which is a noun phrase, and the minor spelling of 'topup' instead of 'top_up'. Otherwise, naming is consistent enough to predict tool behavior.

Tool Count4/5

At 21 tools, this is slightly above the typical 3-15 range, but the broad scope (search, crawling, tracking, media handling, transcripts, remixing, billing) justifies the number. Each tool serves a distinct function, and none feel redundant, so the count is reasonable for the domain.

Completeness3/5

The tool set covers the core workflow well: searching outliers, crawling/tracking profiles, fetching posts/media/transcripts, and generating remixes. However, there is no way to list all posts for a specific profile (only 'recent tracked posts' via get_profile and an incremental feed via get_tracked_updates), which is a notable gap for deep creator analysis.

Resources