SocialDataX 抖音 Douyin MCP

douyin_get_hot_search_list

Read-only

获取抖音主热榜；当前不支持翻页。

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`hot_items`	Yes	抖音主热榜条目

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed9 schema fields changedNov 3, 2026
- addedOutput schema / properties / hot_items / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
- addedOutput schema / properties / hot_items / items / properties / hot_value / title
```
Added value: +"Hot Value"
```
- addedOutput schema / properties / hot_items / items / properties / keyword / title
```
Added value: +"Keyword"
```
- addedOutput schema / properties / hot_items / items / properties / rank / title
```
Added value: +"Rank"
```
- addedOutput schema / properties / hot_items / items / properties / tag / title
```
Added value: +"Tag"
```
- addedOutput schema / properties / hot_items / items / properties / view_count / title
```
Added value: +"View Count"
```
- addedOutput schema / properties / hot_items / items / title
```
Added value: +"DouyinHotSearchItemData"
```
- addedOutput schema / properties / hot_items / title
```
Added value: +"Hot Items"
```
- addedOutput schema / title
```
Added value: +"DouyinHotSearchResult"
```

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / points

Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "hot_items"
-]New value: +[
+  "hot_items",
+  "points"
+]

AddedMay 21, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: 当前不支持翻页 (no pagination), meaning the caller gets a single fixed snapshot and cannot page deeper. It does not mention rate limits, auth, or how fresh the ranking is, so the added context is real but thin.

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?

Two short clauses with zero filler: the purpose first, then the pagination limitation. Every phrase carries information an agent needs, and it is front-loaded so the core function is read first.

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?

Complexity is very low: no parameters, an output schema that documents the return shape, and annotations that cover read-only and open-world behavior. Combined with the no-pagination caveat, the description is sufficient to call the tool correctly; only the ranking semantics (region/refresh cadence) are left unstated.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. The 'no pagination' note is consistent with the empty schema (no page/cursor arguments), reinforcing that the absence of parameters is intentional rather than an omission.

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 states a specific verb+resource: fetch the Douyin main hot-search list (获取抖音主热榜). That is clearly distinguishable from the many sibling detail/search tools, which all target users, videos, products, or comments. It stops short of naming a sibling or explicitly delimiting scope, so it lands at 4 rather than 5.

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 only implied: an agent can infer this is the tool for trending topics rather than for a specific entity, and the phrase 主热榜 signals it covers the main list only. There is no explicit when-to-use/when-not-to-use guidance and no mention of an alternative for related use cases. Adequate but with a clear gap.

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

All SocialDataX 抖音 Douyin MCP 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?