Douyin API New MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| postD | post |
| profileD | profile |
| infoD | info |
| followerD | follower |
| hotvideolistD | hotvideolist |
| susggestwordsD | susggestwords |
| singleD | single |
| itemD | item |
| sugD | sug |
| relatedD | related |
| post_1D | post |
| detailurlD | detailUrl |
| detailD | detail |
| poiD | poi |
| detailidD | detailId |
| channelD | channel |
| listD | list |
| longvideometaD | longVideoMeta |
| hotlistD | hotList |
| replyD | reply |
| discoverD | discover |
| list_1D | list |
| getpcbannerD | getPcBanner |
| brandweeklylistD | brandWeeklyList |
| single_1D | single |
| seokeywordrelatedD | seoKeywordRelated |
| followingD | following |
| cityD | city |
| awemeD | aweme |
| webshortenD | webShorten |
| emojilistD | emojiList |
| chartD | chart |
| aweme_1D | aweme |
| musicD | music |
| challengeD | challenge |
| indexD | index |
| item_1D | item |
| wallpaperD | wallpaper |
| brandbillboardD | brandBillboard |
| mediumrelatedD | mediumRelated |
| nearbyD | nearby |
| tabD | tab |
| lvideotheaterD | lvideoTheater |
| followD | follow |
| detail_1D | detail |
| detail_2D | detail |
| moduleD | module |
| searchlistD | searchList |
| appointlivelistD | appointLiveList |
| queryaccounttypeD | queryAccountType |
| aweme_2D | aweme |
| index_1D | index |
| transD | trans |
| liveD | live |
| sug_1D | sug |
| poi_1D | poi |
| reply_1D | reply |
| list_2D | list |
| socialD | social |
| recommendD | recommend |
| detail_3D | detail |
| list_3D | list |
| abD | ab |
| aweme_3D | aweme |
| brandcategoryD | brandCategory |
| aweme_4D | aweme |
| detail_4D | detail |
| favoriteD | favorite |
| detailurl_1D | detailUrl |
| searchvideolistD | searchVideoList |
| billboardawemeD | billboardAweme |
| detail_5D | detail |
| aweme_5D | aweme |
| selfD | self |
| index_2D | index |
| detail_6D | detail |
| detail_7D | detail |
| suggestwordsD | suggestWords |
| seoinnerlinkD | seoInnerLink |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 79 tools
The tool set is highly ambiguous with numerous duplicate names (e.g., aweme repeated 6 times, detail repeated 8 times, list repeated 4 times) and vague single-word names (e.g., ab, index, item, social) that provide no clear distinction. An agent would struggle to differentiate between tools, leading to frequent misselection due to overlapping or indistinguishable purposes.
Naming conventions are inconsistent, mixing camelCase (e.g., appointLiveList, brandBillboard) with snake_case (e.g., search_videolist is implied but not consistent) and single words (e.g., live, music). There is no predictable pattern across the set, with some tools using verbs (e.g., discover, follow) and others using nouns (e.g., channel, city), creating confusion.
With 79 tools, the count is excessive for a typical MCP server, indicating poor scoping and likely redundancy. This overwhelms the surface area, making it difficult for agents to navigate and increasing the risk of tool misuse. Such a high number suggests fragmentation rather than a cohesive API coverage.
Inferring the domain as Douyin (TikTok) API, the tools cover various aspects like videos (aweme, detail), social features (follow, reply), search (searchlist, suggestwords), and content discovery (hotlist, recommend). However, the redundancy and vague naming make it hard to assess true coverage, but core areas seem represented albeit with potential gaps in specific operations like update or delete actions.