Skip to main content
Glama

Viral Outliers

by com.viraloutliers

Report an Issue

report_issue

Report a problem with any skill: an error you keep hitting, data that looks wrong or stale, or something you needed that the API could not do. Free: never spend credits on telling us something is broken. Include what you called, what you expected and what happened. Set wantsUpdate to true to get an email on your account address when the issue is resolved. Reports go straight to the team. Cost: free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillNoWhich skill the issue is about, when known
messageYesWhat you called, what you expected, what happened (10–2000 chars)
wantsUpdateNotrue = email the account owner when resolved

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (which are all false), the description discloses cost ('Free', 'never spend credits'), that reports 'go straight to the team', and the email notification behavior via wantsUpdate. This adds meaningful context about side effects and behavior not captured in annotations.

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

Conciseness4/5

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

The description is slightly longer than necessary but well-structured: purpose first, then scenarios, cost, instructions, and email option. Every sentence contributes useful information, with no filler.

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 simple reporting tool with no output schema, the description covers key aspects: when to use, what to include, cost, and optional email update. It doesn't discuss rate limits or response behavior, but those are less critical for this type of tool.

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 100%, so the description doesn't need to add much. It does restate the message content and the wantsUpdate behavior, but adds no new technical detail beyond the schema. The 'skill' parameter is implied but not explicitly mapped.

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's purpose: 'Report a problem with any skill' – a specific verb and resource. It distinguishes from siblings by covering error reporting, data issues, and missing API capabilities, which no sibling tool addresses.

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 lists scenarios for use (errors, stale data, missing capabilities) and gives instructions on what to include ('what you called, what you expected and what happened'). It doesn't name alternative tools, but the context makes it clear this is the dedicated reporting tool.

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