TokConnect: TikTok Research

TikTok charts

charts

Read-only

TikTok's own leaderboards. sounds: the music chart (Top 50 or Viral 50; TikTok's chart, not per market). hashtags: trending hashtags in a market over 7, 30 or 90 days, with posts, views and a daily popularity curve (empty for PL, NL and IE). searches: trending search phrases TikTok's website shows. live: TikTok's LIVE leaderboard (daily gifts or LIVE sales), as TikTok's app serves it; not per market. videos: yesterday's top 100 videos in a market with views, organic views, engagement rate and 6-second view rate (TikTok has this list for US, JP, TH, ID and VN; other markets come back empty). Examples: {"method":"hashtags","region":"DE","period":"30"}, {"method":"sounds","chart":"viral"}.

Input Schema

Name	Required	Description	Default
`board`	No	method=live: daily (gift points today, default) or sales (LIVE sales leaderboard).
`chart`	No	method=sounds: top (Top 50, default) or viral (Viral 50).
`limit`	No	Results per page. sounds max 50, hashtags max 50, searches max 100, live max 100, videos max 100. Values above a method's maximum are lowered and reported in notes.
`cursor`	No	Paging: pass the next value from the previous response unchanged. Omit on the first page.
`detail`	No	compact (default) returns the useful fields; full adds the full raw record (large).	compact
`method`	No	What to get. sounds: TikTok's music chart (Top 50 or Viral 50) \| hashtags: trending hashtags in a market (7, 30 or 90 days) \| searches: trending search phrases \| live: LIVE leaderboard (daily gifts or sales) \| videos: yesterday's top 100 videos in a market	sounds
`period`	No	method=hashtags: last 7, 30 or 90 days (default 7).
`region`	No	method=hashtags or videos: market, one of US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX, PL, IT, NL, IE (default US).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / detail / description

Previous value: -"compact (default) returns the useful fields; full adds the raw upstream payload (large)."New value: +"compact (default) returns the useful fields; full adds the full raw record (large)."

AddedOct 31, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the read-only, open-world annotations, the description discloses important behavioral constraints: hashtags are empty for PL, NL and IE, videos only exist for US, JP, TH, ID and VN, and sounds/live are not per market. It does not cover auth or rate-limit behavior, but the availability caveats are valuable.

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 dense but appropriately sized for five methods and numerous caveats, with the high-level purpose front-loaded. The method labels make it scannable, though the semicolon-list format is not maximally structured.

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?

Given the 8 parameters, 100% schema coverage, existing output schema and annotations, the description covers all methods, defaults, examples and key data availability limitations. An agent has enough information to select a method and invoke the tool 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?

Schema coverage is already 100%, so the schema carries most parameter meaning. The description adds useful method-specific context, including examples and the market availability limits that are not fully captured by the schema.

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 clearly identifies the resource as TikTok's own leaderboards and enumerates the five chart types with their scope. It does not explicitly name sibling tools such as hashtag_search or sound_search, so differentiation is implied by 'TikTok's own leaderboards' rather than stated.

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?

The method descriptions give clear context for choosing between sounds, hashtags, searches, live and videos, including defaults and market limitations. However, it does not explicitly say when to use this tool versus sibling search or entity tools.

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

All TokConnect: TikTok Research tools Inspect

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

Need Help?