Contract
input_schema.json
{
"type": "object",
"properties": {},
"additionalProperties": false
}output_schema.json
{
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"word_list": {
"type": "array",
"items": {
"type": "object",
"properties": {
"word": {
"type": "string",
"description": "The trending topic phrase."
},
"label": {
"type": "number",
"description": "Numeric badge/tag code. Meaning undocumented."
},
"group_id": {
"type": "string",
"description": "The topic's public numeric id, as a string. Same class as a public post/media id, not contact data."
},
"max_rank": {
"type": "number",
"description": "Best (highest) rank reached so far."
},
"position": {
"type": "number",
"description": "Current rank in the board."
},
"hot_value": {
"type": "number",
"description": "The topic's heat score."
},
"word_type": {
"type": "number",
"description": "Numeric board-section type code."
},
"event_time": {
"type": "number",
"description": "Unix seconds when the topic appeared on the board."
},
"view_count": {
"type": "number",
"description": "Total views across the topic's content."
},
"video_count": {
"type": "number",
"description": "Videos posted under the topic."
},
"discuss_video_count": {
"type": "number",
"description": "Videos discussing the topic."
},
"article_detail_count": {
"type": "number",
"description": "Related article count."
}
},
"additionalProperties": true
},
"description": "The main ranked hot-search list -- 51 entries on the one calibrated fixture. Entries vary in which fields are present (the top entry in the fixture carries only `word`/`hot_value`/`view_count` and related basics, while ranked entries add `position`/`max_rank`/`event_time`/`group_id`), so every field here is optional."
},
"share_info": {
"type": "object",
"properties": {
"share_title": {
"type": "string",
"description": "The share headline text."
},
"share_link_desc": {
"type": "string",
"description": "The share call-to-action text."
}
},
"description": "Douyin's own share copy for the board.",
"additionalProperties": true
},
"active_time": {
"type": "string",
"description": "The timestamp at which the board was generated, e.g. '2026-09-23 09:11:20' on the one calibrated fixture."
},
"trending_desc": {
"type": "string",
"description": "Label for the \"rising\" section. Observed as \"实时上升热点\" (real-time rising hot topics) on the one calibrated fixture."
},
"trending_list": {
"type": "array",
"items": {
"type": "object",
"properties": {
"word": {
"type": "string",
"description": "The trending topic phrase."
},
"label": {
"type": "number",
"description": "Numeric badge/tag code. Meaning undocumented."
},
"group_id": {
"type": "string",
"description": "The topic's public numeric id, as a string. Same class as a public post/media id, not contact data."
},
"hot_value": {
"type": "number",
"description": "The topic's heat score."
},
"word_type": {
"type": "number",
"description": "Numeric board-section type code."
},
"event_time": {
"type": "number",
"description": "Unix seconds when the topic appeared on the board."
},
"video_count": {
"type": "number",
"description": "Videos posted under the topic."
},
"discuss_video_count": {
"type": "number",
"description": "Videos discussing the topic."
},
"article_detail_count": {
"type": "number",
"description": "Related article count. Absent on some entries."
}
},
"additionalProperties": true
},
"description": "The separately rendered \"rising\" topics -- 5 entries on the one calibrated fixture. Entries carry a sparser field set than `word_list` (some lack `article_detail_count`), so each field is optional."
}
},
"additionalProperties": true
}
},
"description": "The Douyin hot search board, as returned at routing.responseResultPath ($.output).",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.0020475 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 25, 2026