Skip to main content
Glama

creator_search

搜索TikTok达人/创作者。支持按昵称或关键词搜索,可按粉丝数、互动率、带货量等条件筛选。

Args:
    keyword (string): 搜索词
    search_type (string): 搜索方式 N:昵称,K:关键词,默认K
    region (string): 国家/区域,默认US
    category_list (string[]): 达人分类列表
    product_category_list (string[]): 带货分类列表
    fans_cnt_from (integer): 粉丝数量下限
    fans_cnt_to (integer): 粉丝数量上限
    fans_gr_from (number): 粉丝增长率下限
    fans_gr_to (number): 粉丝增长率上限
    interact_from (number): 互动率下限
    interact_to (number): 互动率上限
    avg_like_from (number): 平均点赞量下限
    avg_like_to (number): 平均点赞量上限
    play_cnt_from (integer): 平均播放量下限
    play_cnt_to (integer): 平均播放量上限
    video_cnt_from (integer): 视频数量下限
    video_cnt_to (integer): 视频数量上限
    product_cnt_from (integer): 商品数下限
    product_cnt_to (integer): 商品数上限
    sales_volume_from (integer): 带货销量下限
    sales_volume_to (integer): 带货销量上限
    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
            name (string): 达人昵称
            uniqueId (string): handler_name
            cover (string): 头像地址
            tiktokUrl (string): tiktok链接
            kolspriteUrl (string): kolsprite详情链接
            region (string): 面向区域
            category (string[]): 达人分类
            enCategory (string[]): 达人分类(英文)
            goodsCategory (object[]): 带货分类,元素: {catId(string): 分类ID, catName(string): 分类名称(英文), cnCatName(string): 分类名称(中文)}
            fansCnt (integer): 粉丝数量
            fansGr (number): 粉丝增长率
            likeCnt (integer): 点赞数
            likeFansRate (number): 赞粉比
            interactionRate (number): 互动率
            exposure (number): 视频曝光率
            videoCompletionRate (number): 完播率
            avgLikeCnt (integer): 平均点赞量
            avgViewsPerVideo (integer): 平均播放量
            videoCnt (integer): 视频数量
            lastVideoDate (string): 最后视频发布时间
            productCnt (integer): 带货数
            salesVolume (integer): 带货销量
            gpm (number): 每千次播放销售额
            currency (string): 货币
            mailAddress (string): 邮箱
            contactList (object[]): 联系方式列表,元素: {type(string): 联系方式类型, contactAddress(string): 联系方式地址}

Input Schema

NameRequiredDescriptionDefault
regionNo国家/区域,默认US
keywordNo搜索词
page_numNo页码,默认1
page_sizeNo每页数量,默认20,最大100
fans_gr_toNo粉丝增长率上限
order_typeNo排序方向:0降序,1升序,默认0
avg_like_toNo平均点赞量上限
fans_cnt_toNo粉丝数量上限
interact_toNo互动率上限
order_fieldNo排序字段
play_cnt_toNo平均播放量上限
search_typeNo搜索方式 N:昵称,K:关键词,默认K
fans_gr_fromNo粉丝增长率下限
video_cnt_toNo视频数量上限
avg_like_fromNo平均点赞量下限
category_listNo达人分类列表,只支持传递一个,可选值通过creator_category_list工具查询
fans_cnt_fromNo粉丝数量下限
interact_fromNo互动率下限
play_cnt_fromNo平均播放量下限
product_cnt_toNo商品数上限
video_cnt_fromNo视频数量下限
sales_volume_toNo带货销量上限
product_cnt_fromNo商品数下限
sales_volume_fromNo带货销量下限
product_category_listNo带货分类列表,只支持传递一个,可选值通过product_category_list工具查询

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a solid job: it documents defaults (region=US, search_type=K, page defaults), a hard pagination cap (page_size max 100), and a non-obvious constraint that category_list accepts only one value. It stops short of stating permissions, rate limits, or that this is a read-only operation, but the disclosed constraints are substantive.

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?

The purpose statement is correctly front-loaded and the Returns block earns its place since no output schema exists. However, the 25-line Args section duplicates a schema that is already 100% documented, adding bulk without information.

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

Completeness3/5

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

For a 25-parameter tool with no annotations and no output schema, the description does cover the return structure and cross-references sibling tools for category values. Gaps remain: order_field's accepted values are never specified, and there is no guidance on how filters combine or on required permissions, so an agent can call it but may pick invalid sort fields.

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 baseline is 3. The Args block in the description is essentially a verbatim restatement of the schema descriptions and adds no meaning beyond them (e.g., order_field is left as '排序字段' in both places, with no valid values given).

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 line gives a specific verb and resource ('搜索TikTok达人/创作者') and names the two search modes (nickname vs keyword) plus the filter dimensions, so the agent knows exactly what it retrieves. It does not, however, differentiate itself from the sibling product_related_creator, which also returns creators, leaving a real routing ambiguity unresolved.

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 implied through the search_type semantics ('N:昵称,K:关键词,默认K') and the filter list, which tells the agent this is the broad discovery tool. There is no explicit when-to-use / when-not-to-use statement and no mention of when to prefer product_related_creator or video_search instead.

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