Skip to main content
Glama
DevinChen2014

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_product_detail_by_sku_id

Read-only

Fetch Xiaohongshu product details using a SKU ID. Use it when you already have the sku_id; if not, get it from product search results first.

Instructions

根据小红书商品 sku_id 获取商品详情;已有该 ID 时直接使用,否则可从 xhs_search_products 获取。只有商品链接、短链接或分享文案时使用 xhs_get_product_detail_by_url;本工具不支持商品链接、spu_id 或搜索词。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sku_idYes小红书商品 SKU ID。用户已提供时原样使用;否则从 xhs_search_products 的 items[*].sku_id 原样复制。不支持 spu_id、商品链接或搜索关键词。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYes当前 SKU 的商品原价,单位:元;不是商品搜索的展示销售价,也不是最终实付价
titleYes商品标题
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
sku_idYes商品 SKU ID
shop_idYes店铺 ID
shippingYes发货信息
shop_nameYes店铺名称
assurancesYes商品保障服务列表
sales_textYes平台展示的商品销量文本;没有时为空字符串。带“+”的数量表示下限,不是精确销量;结合 sold_count 解读。
shop_scoreYes店铺评分展示值;没有评分时为空字符串
sold_countYes已售数量;平台以带“+”的千级或万级文本展示时转换为对应整数下限(如“90.2k+ sold”返回 90200、“已售1.2万+”返回 12000),不是精确销量,须结合 sales_text 解读;缺失或无法解析时为 null,不代表零销量;0 表示明确已售 0。
main_imagesYes商品顶部主图/轮播图列表
coupon_priceYes当前 SKU 展示的券后/成交价格,单位:元;不保证是最终实付价
stock_statusYes库存状态码;具体码值含义未公开定义,不要自行解释为是否在售或是否可购买
detail_imagesYes商品详情图列表
shop_fans_textYes店铺粉丝数展示值;没有粉丝信息时为空字符串
shop_sold_textYes店铺已售展示值;没有已售信息时为空字符串
specificationsYes商品属性/规格参数列表(name/value),不是可选 SKU 规格组
shop_avatar_urlYes店铺头像链接
selected_variantYes当前选中规格;没有规格时为空字符串

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.6

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful input-scoping constraints (no links, spu_id, or search terms) and clarifies the ID source, but does not disclose response behavior or error conditions. This is adequate but not exceptional given the annotation coverage.

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?

Two concise sentences front-load the core operation, then cover sourcing the ID and the alternative tool. No redundant wording; every sentence earns its place.

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 simple read-only tool with one parameter, full schema coverage, annotations for safety, and an output schema, the description covers the necessary source guidance and exclusions. Nothing essential 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?

The input schema covers the single parameter 100% with detailed semantics, including exact copying from search results and unsupported input types. The description largely repeats this guidance, so it adds little beyond the schema. Baseline 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 clearly states the tool retrieves product details by sku_id, a specific verb + resource. It also explicitly differentiates itself from xhs_get_product_detail_by_url and lists unsupported identifiers (product links, spu_id, search terms), making its scope unambiguous.

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?

The description explicitly states when to use the tool: directly when sku_id is available, or obtain the ID from xhs_search_products otherwise. It also names the alternative tool for link-based lookups and states exclusions, providing clear routing guidance.

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