Douyin Topic Search & Engagement Stats (by keyword)

omnial/douyin-index-fetch-topic-query

Given a keyword and a date window, returns the Douyin topic-search index for that keyword: every indexed topic that matches, ranked by the platform, with each topic's own item count (posts using it), like count, view/read count, and topic id. A keyword that matches no indexed topic returns just the endpoint's status wrapper rather than an error.

activeper callv2

Price

Up to $0.00205 per call; you pay what the call used

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.00.

Data source

Douyin

Data from Douyin.

Use it

Your AI assistant does the work: it finds this tool, shows you the price first, runs it, and you are charged when the run finishes. There is nothing to set up for this tool in particular.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

For developers: the calls your assistant makes

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/douyin-index-fetch-topic-query" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/douyin-index-fetch-topic-query" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/douyin-index-fetch-topic-query", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/douyin-index-fetch-topic-query", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.00205

Updated: Oct 27, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "end_date",
    "keyword",
    "start_date"
  ],
  "properties": {
    "keyword": {
      "type": "string",
      "description": "Topic keyword"
    },
    "app_name": {
      "enum": [
        "aweme",
        "toutiao"
      ],
      "type": "string",
      "default": "aweme",
      "description": "平台/Platform: aweme(抖音), toutiao(头条)"
    },
    "end_date": {
      "type": "string",
      "description": "End date YYYYMMDD"
    },
    "start_date": {
      "type": "string",
      "description": "Start date YYYYMMDD"
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "properties": {
    "BaseResp": {
      "type": "object",
      "properties": {
        "StatusCode": {
          "type": "number",
          "description": "The endpoint's status code; 0 on both real calls observed."
        },
        "StatusMessage": {
          "type": "string",
          "description": "The endpoint's status message; empty string on both real calls observed."
        }
      },
      "description": "The endpoint's own status wrapper, present on every call observed (matched and no- match alike); its StatusCode is 0 (success) on both real calls.",
      "additionalProperties": true
    },
    "topic_list": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "datetime": {
            "type": "string",
            "description": "A per-topic timestamp field; observed as an empty string on all 99 real entries, so treat an empty string as \"not populated for this topic\" rather than a valid timestamp."
          },
          "digg_cnt": {
            "type": "string",
            "description": "Count of likes on the topic's posts, as a digit string."
          },
          "item_cnt": {
            "type": "string",
            "description": "Count of posts/videos using the topic, as a digit string."
          },
          "topic_id": {
            "type": "string",
            "description": "The platform's numeric topic id (a long digit string, not a phone number) -- the stable identifier for the topic."
          },
          "topic_name": {
            "type": "string",
            "description": "The topic's public label, e.g. a hashtag or a keyword phrase; may itself carry a public figure's name as the topic's subject."
          },
          "topic_index": {
            "type": "string",
            "description": "A numeric string the platform reports alongside the topic; its exact meaning is not documented in the endpoint's schema."
          },
          "play_read_cnt": {
            "type": "string",
            "description": "Count of play/read views across the topic's posts, as a digit string -- a long-digit engagement metric, not a phone number."
          }
        },
        "description": "One indexed topic and its platform-reported engagement counters. All numeric-looking counts are the endpoint's own STRING values, not JSON numbers -- treat them as opaque digit strings from the platform.",
        "additionalProperties": true
      },
      "description": "One entry per indexed topic the keyword matched, ordered by the platform; a broad matched keyword returned 99 entries in testing. Absent entirely on a no-match keyword."
    }
  },
  "description": "The topic-search result. Root shape observed as `{ topic_list: [...], BaseResp: { StatusCode: 0, StatusMessage: \"\" } }` for a keyword with indexed topics, and as `{ BaseResp: { StatusCode: 0, StatusMessage: \"\" } }` alone -- no `topic_list` at all -- for a keyword that matches no indexed topic: the endpoint returns an empty result rather than an error. Nothing in this tool's output is image or URL content.",
  "additionalProperties": true
}