Skip to main content
Glama
Sign In

Viral Outliers

by com.viraloutliers
OverviewDiscussionsAdmin

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 25 profiles returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1-based. A search serves its first 1,000 profiles; a page past that is refused at no charge, so narrow the filters instead.
queryNoHandle, @handle, or profile URL
pageSizeNoResults per page, 1 to 100 (default 25). Billed per 25 profiles returned: 25 costs 1 credit, 100 costs 4.
platformsNo
categoryIdNoNiche filter: a category id from list_categories (covers its subtree); without a query returns that niche's top profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based. A search serves its first 1,000 profiles; a page past that is refused at no charge, so narrow the filters instead."
    • addedInput schema / properties / pageSize / description
      Added value: +"Results per page, 1 to 100 (default 25). Billed per 25 profiles returned: 25 costs 1 credit, 100 costs 4."
  2. Changed1 schema field changed
    • addedInput schema / properties / categoryId
      Added value: +{
+  "description": "Niche filter: a category id from list_categories (covers its subtree); without a query returns that niche's top profiles",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that deactivated profiles are returned by default with frozen stats, that renamed creators can surface as duplicate rows, and the credit cost per 25 profiles returned. These are exactly the non-obvious behaviors an agent needs before calling.

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?

Front-loaded with purpose and return summary, then behavior and cost. Every sentence is informative, though the credit cost is repeated from the pageSize schema entry, creating minor redundancy.

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 compensates by summarizing return values (profile metadata, follower counts, average performance stats) and flags the deactivated/duplicate edge cases. Nothing needed to invoke the tool correctly is missing.

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 description coverage is 80%, so page, pageSize billing, and categoryId are already documented in the schema. The description restates platform filtering and the credit cost but adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb+resource (search tracked social media profiles by handle or name, filtered by platform) and distinguishes its role from the fetch-by-id flow ('resolve a handle to a profile id before fetching stats or posts'). An agent can tell it apart from get_profile or list_tracked_profiles from the description alone.

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?

Gives two concrete use cases (resolve a handle to an id; discover creators in the database) plus a filtering condition (filter on is_active for live accounts only). It stops short of naming an alternative sibling or stating when NOT to use this search, so it is clear context rather than explicit routing.

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