TokConnect: TikTok Research

One hashtag

hashtag

Read-onlyIdempotent

One hashtag (id from hashtag_search or hashtags[].id on a post): detail, its videos (hot or newest), or related hashtags. Example: {"id":"229207","method":"videos","sort":"newest"}.

Input Schema

Name	Required	Description	Default
`id`	Yes	Hashtag id (hashtags[].id).
`sort`	No	method=videos: hot (TikTok's ranking, default) or newest.
`limit`	No	Results per page. videos max 50, related max 20. 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. detail: views, video count, description \| videos: videos using the hashtag \| related: hashtags TikTok relates to it	detail
`region`	No	Market as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions.

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)."

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "Market as an ISO country code, default US. Shop Analytics methods: sales data for that market, amounts in its currency. Live methods that take it (search, video detail, creator posts, Shop pages): TikTok as seen in that market where TikTok serves it. Core: US, GB, DE, FR, ES, JP, TH, VN, ID, MY, PH, BR, MX. Extended: PL, IT, NL, IE. Other countries are refused. See shop_regions.",
+  "maxLength": 2048,
+  "type": "string"
+}

AddedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds little beyond structured fields — the worked example is the main value-add — and says nothing about result volume or how the three methods differ in cost.

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?

One dense sentence plus a compact example, with the id provenance front-loaded. Nothing is wasted, though the sentence packs three concepts tightly enough that it reads as a list rather than guidance.

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?

With an output schema present and full annotation coverage, the description need not explain returns. Combined with the id-source hint and worked example, an agent has enough to call it correctly; only method-selection guidance is thin.

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%, so all seven parameters (including enums for method, sort, detail, and the cursor/limit semantics) are already documented in the schema. The description's example reinforces method=videos with sort=newest but adds no new parameter meaning; baseline 3 applies.

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?

Names the resource (one hashtag) and enumerates the three things it can return — detail, videos, related hashtags — plus where the id comes from. It routes to sibling hashtag_search for id discovery, though the core verb ('get') is implied 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 parenthetical 'id from hashtag_search or hashtags[].id on a post' gives clear context for when this tool is the right call versus the search sibling, and the sample call illustrates a valid mode. It stops short of stating exclusions or tradeoffs between method=detail vs videos vs related.

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?