Skip to main content
Glama
Sign In

Viewlify

by io.github.benjaminb10
OverviewDiscussionsAdmin

get_outliers

TikTok videos beating their own creator's usual views by the widest margin (the real breakouts), optionally for a niche or free-text search. Each result includes the outlier multiple and the creator's baseline (Pro and Agency keys; otherwise a 5-result preview without them).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_outliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-50)
nicheNoNiche slug to focus on
searchNoFree-text query (keyword, creator, hashtag)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does reasonably well: it discloses the key behavioral constraint — Pro/Agency keys return the outlier multiple and creator baseline, while other tiers get a 5-result preview without them. It stops short of stating whether the preview cap overrides the limit parameter or mentioning rate limits, which would strengthen it.

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?

Two tight sentences with the core definition front-loaded and the response/paywall caveat second. Every clause earns its place; the parenthetical 'the real breakouts' is slightly decorative but harmless.

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

Completeness3/5

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

For a 3-param read tool with full schema coverage and no output schema, the description covers the concept and the tier-based behavior. What's missing is how results are ranked or sorted, whether the 5-result preview truncates independently of the limit parameter, and any paging handling for up to 50 results.

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 limit range (1-50) and the niche/search meanings are already documented structurally. The description adds only that niche and search are optional focus filters, which is marginal value beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb+resource: identifies the resource (TikTok videos outperforming their creator's usual views) and the ranking criterion (widest margin over baseline). Says what each result contains. Sibling differentiation isn't explicit — get_trending and get_trending_hashtags are never named — but the 'beating their own creator's usual views' framing is distinctive enough to distinguish conceptually.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: 'optionally for a niche or free-text search' tells how to narrow, and the Pro/Agency note explains what a caller gets back. There is no explicit statement of when to choose this over get_trending, and no guidance on when an unfiltered call versus a niche-filtered call is appropriate.

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

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