Skip to main content
Glama
pangolinfo

PangolinFo Amazon Ad Tracker & Review Intelligence

Official
by pangolinfo

get_amazon_product

Fetch comprehensive Amazon product details by ASIN including price, ratings, seller, and reviews for competitor analysis and ad tracking.

Instructions

[Amazon 单品详情] 按 ASIN 抓某个具体商品的完整 PDP 数据。 Use when: 用户给了具体 ASIN(B0XXXXXXXX)要"看一下这个产品""查它的价格/评分/卖家""分析这个竞品";或 SOP 中拿到候选 ASIN 后需要深拆。 Don't use: 一次想看多个商品的简要对比(用 search_amazon 或 list_* 系列拿列表);只要评论(用 get_amazon_reviews 更专一便宜)。 Returns (format='json', 默认): data.json[0].data.results[0] = { asin, title, price, star, rating, brand, seller{name,id}, parentAsin, ratingDistribution[], aiReviewsSummary, bestSellersRankItems, reviews[{date,star,content,helpful,...}], productOverview[], features[], productDescription[], images[], variantDetails[], attributes[], category_id, breadCrumbs, ... } — 30+ 字段(含 variantDetails 简表)。 Pair with: ↑ asin 常来自 search_amazon / list_bestsellers / filter_niches;↓ 同一 asin 喂 get_amazon_reviews 取更多评论(默认 PDP 只带 5-10 条 reviews)。 Cost: ~1 积点/次, ~5s。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinYesAmazon ASIN,10 位大写字母+数字。Examples: 'B09B8V1LZ3' (Echo Dot 5) / 'B0CRMZHDG8' (Stanley Quencher) / 'B0BDHWDR12' (AirPods Pro 2)。
siteNoAmazon 站点。默认 amz_us(美国站)。amz_us
zipcodeNo邮编,必须匹配 site 站点所在国家(amz_us → 美国邮编,amz_jp → 日本邮编 …)。可选;不传时后端会从对应国家邮编池随机挑一个。跨国邮编(如 amz_us + 日本邮编)会被后端拒绝。Examples: 10001 (NY) / 90001 (LA) / 100-0001 (Tokyo).
formatNo返回格式。默认 'json'——结构化字段(title/price/rating/reviews/seller 等),适合程序处理。需要原始页面阅读时切 'markdown'。json
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses cost ('~1 积点/次, ~5s'), default review count (5-10), and return structure (30+ fields). Could mention rate limits or idempotency, but current info is sufficient.

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

Conciseness4/5

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

Description is longer but well-structured with clear sections (use when/don't use, returns, pairing, cost). Front-loaded with main purpose. Could be slightly more concise, but every sentence adds value.

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 details the return structure (30+ fields listed). Combined with schema coverage and context signals (4 params, 17 siblings), the description is complete enough for an agent to understand the tool's full behavior and output.

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 already covers all 4 parameters (100% coverage). The description adds significant value: examples for asin, full list for site, usage notes for zipcode (matching, random fallback, rejection), and format use cases. This goes well beyond 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 clearly states the tool's purpose: to fetch complete PDP data for a specific Amazon ASIN. It uses a specific verb ('抓') and resource ('单品详情'), and distinguishes itself from sibling tools like search_amazon and get_amazon_reviews by specifying scope.

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?

Explicitly tells when to use: '用户给了具体 ASIN ... 要看一下这个产品' and when not to use: '一次想看多个商品的简要对比' or '只要评论', with alternatives provided. Also mentions pairing with other tools for extended analysis.

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