Skip to main content
Glama
pangolinfo

PangolinFo Amazon Ad Tracker & Review Intelligence

Official
by pangolinfo

list_bestsellers

Retrieve Amazon Best Sellers top 100 for any category, including 24-hour sales rank changes. Analyze category leaders and track ranking shifts.

Instructions

[Amazon 热销榜] 拉某类目的 Best Sellers Top-100,含 24h 排名变化。 Use when: 用户说"X 类目热销榜""哪些是该类目龙头""有没有黑马冲上来""benchmark 卖得最好的产品";选品时定基准品;竞品雷达里追踪类目龙头排名变化。 Don't use: 看新品(用 list_new_releases);想要类目下完整商品列表而非 Top 100(用 list_category_products);只知道关键词不知道类目(用 search_categories 先找类目)。 Returns: data.json[0].data.{ reftag, recsList } — recsList 是字符串形式的 JSON 数组,需要二次 parse;每条 { id, metadataMap.{ render.zg.rank, currentSalesRank, percentageChange, twentyFourHourOldSalesRank } }。 Pair with: ↑ categorySlug 需要用户提供或从场景推测(如 'electronics' / 'home-garden' / 'beauty');↓ 把 id (ASIN) 喂 get_amazon_product 拆单品。 Cost: ~1 积点/次, ~5s。 Tips: categorySlug 是 Amazon URL 路径里的英文短横线串,从 amazon.com/Best-Sellers 顶部导航能看到。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categorySlugYesAmazon Best Sellers 类目 slug(小写英文短横线),如 'electronics'、'home-garden'、'beauty'、'toys-and-games'。可以从 amazon.com/Best-Sellers 顶部导航的 URL 路径里读到。
siteNoAmazon 站点。默认 amz_us。amz_us
zipcodeNo邮编,必须匹配 site 站点所在国家(amz_us → 美国邮编,amz_jp → 日本邮编 …)。可选;不传时后端会从对应国家邮编池随机挑一个。跨国邮编(如 amz_us + 日本邮编)会被后端拒绝。Examples: 10001 (NY) / 90001 (LA) / 100-0001 (Tokyo).
formatNo返回格式。默认 'json'——结构化 Top-100 ASIN 排名列表。需要原始页面阅读时切 'markdown'。json
Behavior5/5

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

With no annotations, the description carries full burden. It details the return structure, notes that recsList requires JSON parsing, lists fields, and provides cost/time estimates. It implies a read-only operation and discloses all behavioral traits.

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?

Well-structured and front-loaded: summary, usage guidance, return details, pairing, cost, tips. Every sentence contributes essential information without redundancy.

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?

Given no output schema, the description thoroughly explains return format and fields. It also provides alternatives, usage context, and operational nuances (cost, speed, parsing requirement). Completely covers what an agent needs to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value: explains how to obtain categorySlug from URL, clarifies zipcode matching and randomization, gives format examples. This exceeds the schema descriptions.

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 starts with a specific verb ('拉' = retrieve) and resource ('Best Sellers Top-100 for a category'), and mentions 24h rank changes. It distinguishes from siblings by explicitly listing when to use and not use alternative tools.

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?

Explicit 'Use when' and 'Don't use' sections with concrete examples and named alternatives (list_new_releases, list_category_products, search_categories). Provides clear context for selecting this tool over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pangolinfo/pangolinfo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server