Skip to main content
Glama

asin_analysis_video

ASIN关键词视频分析。根据ASIN和市场区域查找关联的带货视频。

Args:
    market (string): 市场(US/GB/...),必填
    asin (string): 亚马逊ASIN标识,必填
    region (string): 视频区域,非必传,不传则和market一致
    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): 互动率
            currency (string): 货币
            totalSalesVolume (integer): 总销量
            salesVolumeLst30d (integer): 近30天销量
            salesLst30d (number): 近30天销售额
            creator (object): 达人信息
            product (object): 商品信息
        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
asinYes亚马逊ASIN标识,必填
marketYes市场(US/GB/...),必填
regionNo视频区域,非必传,不传则和market一致
page_numNo页码,默认1
page_sizeNo每页数量,默认20,最大100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the paginated return shape and field semantics. However, it never states that this is a read-only lookup, nor does it mention auth requirements or rate limits, so the operational profile is only inferable.

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 is front-loaded, which is good, but the Args block is a pure duplicate of the input schema and does not earn its place. The Returns block is long yet justified since there is no output schema; the parameter repetition is the main waste.

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?

Because no output schema exists, the detailed nested return documentation (pagination wrapper, video fields, creator and product sub-objects) genuinely compensates and lets an agent consume the result. The remaining gap is the absence of any routing context against the sibling video tools.

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%, so the schema already documents every parameter. The Args block in the description merely restates the same text verbatim (e.g. '市场(US/GB/...),必填'), adding no syntax, valid-value, or fallback detail 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 Chinese description states a concrete verb and resource: retrieve sales/带货 videos associated with a given ASIN and market region. This is more specific than a bare resource name, but it never distinguishes itself from siblings such as video_search or product_related_creator, which an agent must disambiguate against.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and names no alternative. Nothing tells the agent why it would pick this over video_search or product_related_creator, even though those siblings clearly overlap.

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