Skip to main content
Glama

Viral Outliers

by com.viraloutliers

List Monitored Profiles

list_tracked_profiles
Read-onlyIdempotent

Returns every profile you are currently monitoring, with its handle, platform, follower count, refresh cadence, next scheduled crawl time, when it was last checked for updates, and any paused reason (e.g. paused for insufficient credits). Free to call. Use it to audit what is being refreshed and what it is costing, or to grab a profileId for untrack_profile. Cost: free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds value by disclosing cost ('Free to call'), output fields, and paused-reason context, which go beyond the annotations. No contradiction.

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 first sentence is a long run-on listing many fields, and cost is mentioned twice ('Free to call' and 'Cost: free'), creating redundancy. It is structured but could be tightened.

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?

For a parameterless tool with no output schema, the description thoroughly covers what is returned, why to use it, and cost. It fully equips an agent to select and invoke this tool.

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 tool has zero parameters, so the baseline is 4. The description adds meaning by enumerating the return fields, though it does not need to explain parameters that do not exist.

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 clearly states the tool returns every monitored profile with specific fields, and the focus on profile list distinguishes it from siblings like get_tracked_updates. The verb 'Returns' and resource 'every profile you are currently monitoring' are specific and unambiguous.

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 provides explicit use cases: auditing refresh status/cost and grabbing a profileId for untrack_profile. However, it does not mention alternatives or when not to use it, such as differentiating from get_tracked_updates.

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