Skip to main content
Glama

video_search

搜索TikTok带货视频。支持按关键词搜索,可按播放量、点赞、销量、时长等条件筛选。

Args:
    keyword (string): 搜索词
    region (string): 国家/区域,默认US
    video_ids (string[]): 视频id查询,最大50
    video_type (string): 视频类型
    product (boolean): 是否带货视频
    product_id (string): 商品id
    shop_id (string): 店铺id
    product_category_list (string[]): 带货分类列表
    play_cnt_from (integer): 播放量下限
    play_cnt_to (integer): 播放量上限
    like_cnt_from (integer): 点赞量下限
    like_cnt_to (integer): 点赞量上限
    interact_from (number): 互动率下限
    interact_to (number): 互动率上限
    price_from (number): 价格下限
    price_to (number): 价格上限
    sales_volume_from (integer): 销量下限
    sales_volume_to (integer): 销量上限
    sales_volume_lst30d_from (integer): 近30天销量下限
    sales_volume_lst30d_to (integer): 近30天销量上限
    sales_lst30d_from (number): 近30天销售额下限
    sales_lst30d_to (number): 近30天销售额上限
    seconds_from (integer): 时长下限(秒)
    seconds_to (integer): 时长上限(秒)
    pub_date_from (string): 发布时间起始,格式yyyy-MM-dd(如2024-01-01)
    pub_date_to (string): 发布时间截止,格式yyyy-MM-dd(如2024-12-31)
    order_field (string): 排序字段
    order_type (integer): 排序方向:0降序,1升序,默认0
    page_num (integer): 页码,默认1
    page_size (integer): 每页数量,默认20,最大100

Returns:
    object: 分页结果。
        外层: {code(string): 状态码, message(string): 提示信息, success(boolean): 是否成功, data(object): 分页数据}
        data: {total(integer): 数据总数, pageNum(integer): 当前页码, pageSize(integer): 页容, list(object[]): 结果集}
        list元素(视频):
            id (string): 视频ID
            title (string): 视频标题
            cover (string): 视频封面
            region (string): 区域
            seconds (integer): 视频时长(秒)
            pubTime (string): 视频发布时间
            playCnt (integer): 播放量
            likeCnt (integer): 点赞数
            collectCnt (integer): 收藏数
            commentCnt (integer): 评论数
            forwardCnt (integer): 转发数
            interactionRate (number): 互动率
            vqScore (string): 质量得分
            currency (string): 货币
            totalSalesVolume (integer): 总销量
            salesVolumeLst30d (integer): 近30天销量
            salesLst30d (number): 近30天销售额
            creator (object): 达人信息
            product (object): 商品信息
            tiktokUrl (string): tiktok链接
            kolspriteUrl (string): kolsprite详情链接
        creator(达人信息):
            id (string): 达人ID
            name (string): 达人昵称
            handleName (string): 达人handle
            cover (string): 达人头像
            region (string): 达人区域
            fansCnt (integer): 粉丝数
            categoryList (string[]): 达人分类
            enCategoryList (string[]): 达人英文分类
        product(商品信息):
            id (string): 商品ID
            title (string): 商品标题
            imageUrl (string): 商品图片
            price (number): 现价
            originalPrice (number): 原价
            currency (string): 货币
            region (string): 商品区域
            catId (string): 分类ID
            catName (string): 分类名称
            cnCatName (string): 中文分类名称
            salesVolumeLst30d (integer): 近30天销量
            totalSales (number): 总销售额

Input Schema

NameRequiredDescriptionDefault
regionNo国家/区域,默认US
keywordNo搜索词
productNo是否带货视频
shop_idNo店铺id
page_numNo页码,默认1
price_toNo价格上限
page_sizeNo每页数量,默认20,最大100
video_idsNo视频id查询,最大50
order_typeNo排序方向:0降序,1升序,默认0
price_fromNo价格下限
product_idNo商品id
seconds_toNo时长上限(秒)
video_typeNo视频类型
interact_toNo互动率上限
like_cnt_toNo点赞量上限
order_fieldNo排序字段
play_cnt_toNo播放量上限
pub_date_toNo发布时间截止,格式yyyy-MM-dd(如2024-12-31)
seconds_fromNo时长下限(秒)
interact_fromNo互动率下限
like_cnt_fromNo点赞量下限
play_cnt_fromNo播放量下限
pub_date_fromNo发布时间起始,格式yyyy-MM-dd(如2024-01-01)
sales_lst30d_toNo近30天销售额上限
sales_volume_toNo销量上限
sales_lst30d_fromNo近30天销售额下限
sales_volume_fromNo销量下限
product_category_listNo带货分类列表,只支持传递一个,可选值通过product_category_list工具查询
sales_volume_lst30d_toNo近30天销量上限
sales_volume_lst30d_fromNo近30天销量下限

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose useful limits and defaults (region defaults to US, video_ids max 50, page_size default 20 / max 100, order_type default 0), but says nothing about authentication, rate limits, or whether an empty keyword is allowed. The detailed Returns block adds real value that annotations would otherwise have to supply.

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

Conciseness3/5

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

Front-loading the one-sentence purpose is good, and the Returns section is justified because no output schema exists. However, the 30-line Args block duplicates parameters already documented at 100% coverage in the schema, so a large portion of the text does not earn its place.

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?

For a 30-parameter search tool with no output schema, the embedded Returns block fully documents the pagination envelope and nested video/creator/product objects, which is exactly the missing structured data. Gaps remain around auth/permission requirements and the valid values for order_field and video_type, but nothing critical to a correct call is absent.

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 already 100%, so the schema documents all 30 parameters. The Args block largely restates those same descriptions and actually omits the schema-only detail that product_category_list accepts only one value. Baseline 3 applies since the description adds no syntax or format meaning beyond the schema.

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

Purpose4/5

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

The opening sentence gives a specific verb+resource: searching TikTok product-selling videos, with keyword search and metric filters. An agent can tell it is a video-level search distinct from product_search, creator_search and shop_search by resource, though the description never names or contrasts those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the parameter list — it is a filtered search over videos. The only real routing hint is the cross-reference that valid product_category_list values come from the product_category_list tool. There is no when-to-use/when-not guidance against the eight sibling tools.

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