SocialDataX 抖音 Douyin MCP

douyin_search_videos

Read-only

搜索抖音视频和图文作品。用户需要按搜索词查找作品时使用；已有作品链接或 aweme_id 且需要单篇信息时使用相应详情、评论或口播转文字工具；作品通常为视频，也可能包含图文内容；支持 page_token 翻页。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`keyword`	Yes	搜索词，可传关键词或短语，例如品牌名、话题、人物名或产品名；不要传作品链接、用户主页链接、aweme_id、sec_user_id 或 page_token。
`sort_type`	No	搜索排序方式，可选：general（综合，默认）、time_descending（最新发布优先）、like_count_descending（最多点赞优先）。综合或默认排序请传 general，最新发布请传 time_descending，最多点赞请传 like_count_descending。hot、latest、time、relevance、relevance_desc、default、综合、general_desc、liked、like_count、liked_desc、most_liked、most_hot、popularity_descending 等写法均不是可接受值，请直接使用上述三个标准值。	general
`page_token`	No	page_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一搜索链路，不能跨能力、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。
`content_type`	No	内容形式筛选，可选：all（不限，默认）、video（视频）、image（图文）。如无明确筛选需求，保持 all。	all
`duration_range`	No	视频时长筛选，可选：all（不限，默认）、under_1_minute（1 分钟以下）、one_to_five_minutes（1-5 分钟）、over_5_minutes（5 分钟以上）。如无明确筛选需求，保持 all。	all
`publish_time_range`	No	发布时间范围筛选，可选：all（不限，默认）、day（一天内）、week（一周内）、half_year（半年内）。如无明确筛选需求，保持 all。	all

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	当前页搜索结果中的作品列表
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and openWorldHint, so the description's main added behavioral value is noting that results may include image-text works despite the 'videos' name, and that pagination via page_token is supported. This is useful but not extensive; the schema already documents the page_token mechanics.

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?

The description is two tight sentences that front-load the core purpose, then add usage routing, content-type nuance, and pagination support. Every sentence earns its place with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with an output schema, rich parameter schema, and safety annotations, the description covers purpose, when to use it, key content-type nuance, and pagination. Nothing needed for correct invocation or tool selection is missing.

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%, and the schema itself provides very detailed parameter descriptions, including accepted enum values and invalid alternatives. The description adds minimal parameter-level meaning beyond repeating that page_token pagination exists, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (搜索) and resource (抖音视频和图文作品), and explicitly positions it as the tool for searching by keyword, distinguishing it from detail/comment/speech tools used when a link or aweme_id is already available. This makes its purpose clear and differentiates it from siblings without requiring schema inspection.

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?

It gives explicit when-to-use guidance ('用户需要按搜索词查找作品时使用') and names alternative tools for single-item lookups by link/aweme_id. However, it does not explicitly exclude the sibling search tools douyin_search_products and douyin_search_users, though '作品' and the resource phrasing imply they are separate.

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