Skip to main content
Glama
Sign In

Viewlify

by io.github.benjaminb10
OverviewDiscussionsAdmin

get_trending

Trending TikTok videos, hashtags and sounds breaking out right now, optionally filtered to a niche. Ranked by view velocity over real public data. Without an API key: a 5-result preview.

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_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoNiche slug, e.g. beauty, gaming, food, fitness

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real context: results are ranked by view velocity, sourced from real public data, and unauthenticated callers get a capped 5-result preview. That preview cap is exactly the kind of limit an agent needs before calling. Missing is any mention of how to supply a key or whether results are cached/paginated.

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?

Three short sentences with zero filler: resource and scope first, then ranking method and data provenance, then the access limit. The most decision-relevant constraint (ranked by velocity, preview cap) is placed where an agent will read it.

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 single optional-parameter read tool with no output schema, the description covers purpose, ranking, data source, and an access limitation. It never describes the shape of returned items (fields per video/hashtag/sound), which is the one substantive gap for an agent that must consume the result.

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 100% and the single optional category parameter is documented with example slugs, so the description adds nothing beyond it. The phrase 'optionally filtered to a niche' merely restates 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?

The description names a specific resource (trending TikTok videos, hashtags and sounds), a time scope (breaking out right now), and a ranking basis (view velocity). It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like get_trending_hashtags, which appears to overlap with the hashtag portion of this tool's output.

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 — discovery of currently-breaking trends, optionally narrowed to a niche — and the no-API-key preview clause hints at an access tier. However, there is no explicit when-to-use versus when-to-pick get_trending_hashtags or get_outliers guidance, leaving the agent to infer routing from names alone.

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