Skip to main content
Glama
pangolinfo

Amazon All-in-One Scrape MCP

Official
by pangolinfo
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Hybrid

list_new_releases

Retrieve the top-50 best-selling ASINs launched within the last 30 days for any Amazon category. Use to monitor new product entrants and trending directions.

Instructions

[Amazon New Releases] Best-selling Top-50 ASINs that hit the market within the last 30 days for a category (backend cap; not 100). Use when: user says "new arrivals in X" / "any breakout new products" / "newly-launched that sell well" / "trending new directions" / "new entrants to monitor"; GTM scouting for new angles; competitor radar catching new entrants. Don't use: for evergreen winners (use list_bestsellers); for full category listings (use list_category_products); when you only have a keyword (use search_categories first). Returns: data.json[0].data.{ reftag='zg_bsnr_g_', recsList } — recsList is a JSON-string array (parse twice); each row { id, metadataMap.{ render.zg.rank, ... } }. Pair with: ↑ categorySlug as in list_bestsellers; ↓ feed id (ASIN) into get_amazon_product to see why it climbed (pitch, pricing, variant strategy). Cost: ~1 point/call, ~5s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categorySlugYesAmazon New Releases category slug (lowercase, hyphenated). Examples: 'electronics', 'home-garden'. Find these in the URL path on amazon.com/gp/new-releases.
siteNoAmazon marketplace. Defaults to amz_us.amz_us
zipcodeNoZIP code that must match the site country (amz_us → US zip, amz_jp → JP zip, ...). Optional; backend picks a random one from the per-country pool when omitted. Cross-country zips (e.g. amz_us + JP zip) are rejected by the backend. Examples: 10001 (NY) / 90001 (LA) / 100-0001 (Tokyo).
formatNoResponse format. Defaults to 'json' — structured ranking list. Use 'markdown' for the rendered page text.json

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.7.3
    • changedInput schema / properties / categorySlug / description
      Previous value: -"Amazon New Releases 类目 slug（小写英文短横线），如 'electronics'、'home-garden'。可以从 amazon.com/gp/new-releases 顶部导航的 URL 路径里读到。"New value: +"Amazon New Releases category slug (lowercase, hyphenated). Examples: 'electronics', 'home-garden'. Find these in the URL path on amazon.com/gp/new-releases."
    • changedInput schema / properties / format / description
      Previous value: -"返回格式。默认 'json'——结构化新品榜单。需要原始页面阅读时切 'markdown'。"New value: +"Response format. Defaults to 'json' — structured ranking list. Use 'markdown' for the rendered page text."
    • changedInput schema / properties / site / description
      Previous value: -"Amazon 站点。默认 amz_us。"New value: +"Amazon marketplace. Defaults to amz_us."
    • changedInput schema / properties / zipcode / description
      Previous value: -"邮编，必须匹配 site 站点所在国家（amz_us → 美国邮编，amz_jp → 日本邮编 …）。可选；不传时后端会从对应国家邮编池随机挑一个。跨国邮编（如 amz_us + 日本邮编）会被后端拒绝。Examples: 10001 (NY) / 90001 (LA) / 100-0001 (Tokyo)."New value: +"ZIP code that must match the site country (amz_us → US zip, amz_jp → JP zip, ...). Optional; backend picks a random one from the per-country pool when omitted. Cross-country zips (e.g. amz_us + JP zip) are rejected by the backend. Examples: 10001 (NY) / 90001 (LA) / 100-0001 (Tokyo)."
  2. First observedv0.2.1

TDQS

A4.9/5.0
Behavior5/5

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

In the absence of annotations, the description fully discloses behavior: backend cap, cost (~1 point/call, ~5s), and detailed return structure including parsing instructions for recsList. No contradictions.

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?

Despite length, description is well-structured with clear sections (what, use when, don't use, returns, pair with, cost). Each sentence adds value; no 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 4 parameters and no output schema, the description provides complete guidance: param details, return format with parsing, pairing suggestions, and cost. All necessary information for correct invocation is present.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds extra context (e.g., where to find categorySlug, cross-country zip rejection, format usage). This goes beyond the schema descriptions, justifying a score above baseline 3.

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 it returns the top-50 best-selling new releases (within 30 days) for a category, with explicit mention of 'Amazon New Releases' and backend cap. It distinguishes from siblings by specificity to new releases.

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 lists when to use (e.g., 'new arrivals', 'breakout new products') and when not to use (e.g., 'for evergreen winners use list_bestsellers'). Provides clear alternatives and context.

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