Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

douyin_search_products

Read-only

用户需要按关键词查找抖音全局搜索中的商品时使用;支持排序、价格、服务和卖点筛选,返回归一化商品列表与不透明分页令牌。当前服务提供详情工具时:已有 product_id 时直接使用 douyin_get_product_detail_by_product_id;已有商品链接或分享文案时使用 douyin_get_product_detail_by_url。不用于搜索作品或用户,也不表示商城频道内完整搜索链路。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "douyin_search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes抖音商品搜索词,必填,去除首尾空白后不能为空;可传关键词或短语,例如“iPhone 16”或“露营桌”;keyword 只传搜索词,不要传商品链接、抖音平台对象 ID(如 sku_id、promotion_id、aweme_id、sec_user_id)或 page_token;不要把价格、排序或服务条件拼进 keyword,请使用对应筛选参数。
max_priceNo最高价格,正整数,单位:元;必须大于 0,不传表示不限;与 min_price 同时传入时不得小于 min_price。
min_priceNo最低价格,正整数,单位:元;必须大于 0,不传表示不限;与 max_price 同时传入时不得大于 max_price。
only_liveNotrue 时仅返回当前正在直播的商品(抖音原生筛选“直播中”);false 表示不限(默认)。
sort_typeNo商品排序:general(综合,默认)、sales_descending(销量降序)、price_ascending(价格升序)、price_descending(价格降序)。general
page_tokenNopage_token 是不透明分页令牌。首次请求留空;继续翻页时必须将上一次返回的完整 next_page_token 原样传入,作为 page_token 使用;只能用于同一抖音商品搜索链路、关键词、排序和筛选条件,不能跨能力复用;翻页时 keyword、sort_type、min_price、max_price 及全部筛选参数必须与上一页保持一致;需要修改任一条件时,清空 page_token 后从第一页重新搜索;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。
selling_pointNo卖点筛选:all(不限,默认)、high_sales(月销过万)、high_rating(好评多)。all
official_storeNotrue 时仅返回带“抖音旗舰”标识的商品;false 表示不限(默认)。
seven_day_returnNotrue 时仅返回支持 7 天无理由退货的商品;false 表示不限(默认)。
shipping_insuranceNotrue 时仅返回支持运费险的商品;false 表示不限(默认)。
dispatch_within_24hNotrue 时仅返回支持 24 小时内发货的商品;false 表示不限(默认)。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed13 schema fields changed
    • addedOutput schema / properties / items / items / properties / card_type / title
      Added value: +"Card Type"
    • addedOutput schema / properties / items / items / properties / image_url / title
      Added value: +"Image Url"
    • addedOutput schema / properties / items / items / properties / live_room_id / title
      Added value: +"Live Room Id"
    • addedOutput schema / properties / items / items / properties / price / title
      Added value: +"Price"
    • addedOutput schema / properties / items / items / properties / product_id / title
      Added value: +"Product Id"
    • addedOutput schema / properties / items / items / properties / shop_id / title
      Added value: +"Shop Id"
    • addedOutput schema / properties / items / items / properties / sku_id / title
      Added value: +"Sku Id"
    • addedOutput schema / properties / items / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / items / items / properties / video_id / title
      Added value: +"Video Id"
    • addedOutput schema / properties / items / items / title
      Added value: +"DouyinMallSearchItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"DouyinMallSearchResult"
  4. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / price / description
      Previous value: -"商品卡展示价格,单位:元"New value: +"商品卡展示价格,单位:元;不保证是最终实付价"
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add nuance, which it does by noting the returned normalized list, the opaque token, and the caveat that results are not the complete mall-channel search chain. It stops short of describing pagination state requirements, though those are covered thoroughly in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite use case is front-loaded, followed by the routing rules and then the exclusions, which is a logical order. Three dense sentences, though the routing clauses could be trimmed slightly without losing clarity.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers scope, alternatives, and high-level filter categories for an 11-parameter tool. The main remaining gap is that the high-level mention of filters does not map to specific behaviors, but the schema fully compensates.

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 every parameter (keyword constraints, price bounds, sort enum, selling-point enum, boolean service filters, page_token rules) is fully documented there. The description only summarizes that sorting, price, service and selling-point filters exist, adding no syntax or constraint detail beyond the schema.

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?

States a specific verb and resource: keyword-based lookup of products in Douyin global search, returning a normalized product list plus an opaque pagination token. It immediately contrasts this with searching works or users, and explicitly disclaims being a full mall-channel search pipeline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this when the user needs keyword product search; if a product_id already exists use douyin_get_product_detail_by_product_id, and if a link or share text exists use douyin_get_product_detail_by_url. It also names what the tool is not for (videos, users), so the agent can pick correctly among siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources