Skip to main content
Glama

List TT Trends

list_tt_trends
Read-onlyIdempotent

[read] TikTok trends through the TikTok Trends gateway. type: HASHTAGS (search hashtags, keyword required), USERS (search accounts, keyword required; rows carry unique_id, nickname, follower_count, verified, profile_url), MUSIC (trending sounds, or a sound search with keyword), CATEGORIES or EFFECTS (TikTok's trending lists). Answers {items, next_cursor, has_more, trending, type}; the first page is one priced search, later pages (cursor > 0) are free. HASHTAGS also answers hashtag (the best match), its videos (aweme_id, title, user_id, video_url) and users (user_id, username, nickname of those authors).

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": "list_tt_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoHASHTAGS
countNo
cursorNo
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds information annotations cannot express: the cost model (first page is one priced search, cursor > 0 pages are free) and the shape of the response envelope. It does not discuss error handling, rate limits, or when a keyword misses.

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 the action and gateway, then organised by parameter and by mode; almost every clause carries load-bearing detail. The backtick-telegraphic style is dense but readable, and only the extra HASHTAGS return-field sentence feels tacked onto the end.

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?

There is no output schema, and the description compensates by spelling out the returned keys (`items, next_cursor, has_more, trending, type`) plus the HASHTAGS-specific `hashtag`, `videos`, and `users` payloads. Combined with the cost/pagination note, an agent has everything needed to call it correctly.

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?

With 0% schema description coverage, the description carries the burden: it defines all `type` values, explains when `keyword` is required, and clarifies that `cursor` > 0 means a free continuation page. The `count` parameter is never mentioned, which is the one clear gap.

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 opens with a specific verb and resource ("[read] TikTok trends through the TikTok Trends gateway") and enumerates the five modes of the `type` parameter, so the scope is unmistakable. It stops just short of 5 because it never names the neighbouring tools (search_tt_videos, get_tt_trend_analysis, list_tt_videos) that an agent might otherwise confuse it with.

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?

Each mode carries its own usage cue (HASHTAGS = search hashtags, USERS = search accounts, MUSIC = trending sounds or a sound search, CATEGORIES/EFFECTS = trending lists), and the keyword requirement is stated per mode. There is no explicit "use X instead when..." routing or exclusion, which keeps it below 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.