Skip to main content
Glama
pangolinfo

Amazon All-in-One Scrape MCP

Official

filter_niches

Filter Amazon niches by 50+ commercial metrics to find blue oceans, high-search low-competition, or low-return segments. Use for niche scouting and deep reports.

Instructions

[Amazon niche filter] Filter Amazon Niches (a finer-grained "demand cluster" than categories) by 50+ commercial metrics, or use as a "niche detail" endpoint for one niche. Use when: user says "find blue ocean" / "high search volume + low competition niches" / "fast-growing small markets" / "niche scouting" / "give me the deep report on this niche" / "low return-rate niches" / "niches with return rate under 10%"; the core filter step of GTM scouting SOPs; getting fee structure / brand age / new-launch trends for one niche. Don't use: for full categories (use filter_categories); for actual products in a niche (the niche record only carries 1 referenceAsin; combine with categoryId + list_category_products); for plain keyword search (use search_amazon). Returns: data.items.data[{ nicheId, nicheTitle, referenceAsinImageUrl, currency, searchVolumeT90, searchVolumeT360, searchVolumeGrowthT90, minimumPrice, maximumPrice, avgPrice, productCount, sponsoredProductsPercentage, primeProductsPercentage, top5ProductsClickShare, top20BrandsClickShare, brandCount, sellingPartnerCount, avgBrandAge, avgBestSellerRank, avgProductPrice, avgReviewCount, avgReviewRating, avgDetailPageQuality, newProductsLaunchedT180/T360, successfulLaunchesT90/T180/T360, returnRateT360, fee fields T365 … 100+ fields }] + data.items.pagination.{ total, page, size, hasNext }. Pagination: use the 'page' param (default 1, 1-based, size capped at 10 (default 3)); 'pagination.hasNext=true' means more pages exist, 'hasNext=false' means last page. Pair with: ↑ marketplaceId required (defaults US); nicheTitle for keyword filter, nicheId for single-niche detail; ↓ feed referenceAsin into get_amazon_product to see the representative product; niche doesn't carry a categoryId directly — derive separately if needed. Cost: ~1 point/call, ~5s. Tips: size capped at 10 (default 3); pass long-tail filters (50+ fields) via extraFilters; classic blue-ocean combo = high searchVolumeT90Min + low top5ProductsClickShareT360Max + moderate productCountMax + positive searchVolumeGrowthT90Min + returnRateT360Max ≤ 0.10 (low-return). For return-rate filtering use returnRateT360Max (upper bound, 0-1 decimal); the response includes returnRateT360 with the actual return rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketplaceIdNoAmazon marketplace id (required). Common: US, UK, DE, JP, FR, IT, ES, CA. Defaults to US.US
nicheIdNoWhen set, returns the full deep report for that single niche (this endpoint doubles as the niche-detail endpoint). Omit to list multiple niches matching the filters. Example: '8140a265-768d-4679-8bc2-994cb1c96f0b' (UUID).
nicheTitleNoKeyword match against niche titles. Examples: 'iphone 16 wallet case' / 'wireless earbuds for sports'.
pageNoPage number, 1-based.
sizeNoPage size, max 10 (backend hard limit), default 3 (small default to keep responses under AI context limits — pass size=10 explicitly when you need a wider sweep).
sortFieldNoSort field; any response field name is accepted (e.g. 'searchVolumeT90', 'avgProductPrice').
sortOrderNoSort order: 'asc' or 'desc'.
searchVolumeT90MinNoMin search volume over last 90 days.
searchVolumeT90MaxNoMax search volume over last 90 days.
searchVolumeT360MinNoMin search volume over last 360 days.
searchVolumeT360MaxNoMax search volume over last 360 days.
searchVolumeGrowthT90MinNoMin 90-day search-volume growth rate (decimal, 0.1 = +10%).
searchVolumeGrowthT90MaxNoMax 90-day search-volume growth rate.
minimumPriceMinNoLower bound on the niche's minimum product price.
maximumPriceMaxNoUpper bound on the niche's maximum product price.
productCountMinNoMin product count in the niche.
productCountMaxNoMax product count in the niche.
avgReviewCountMinNoMin average review count.
avgReviewCountMaxNoMax average review count — lower means less competition.
avgReviewRatingMinNoMin average review rating (0-5).
top5ProductsClickShareT360MaxNoMax top-5-products click share over 360 days (0-1). Lower = more fragmented niche, more opportunity.
returnRateT360MaxNoMax return rate over 360 days (0-1).
extraFiltersNoPass-through for any other upstream filter (e.g. sponsoredProductsPercentageT360Min, successfulLaunchesT360Max, avgBestSellerRankMax). Keys must match the upstream doc verbatim.

Schema Changelog

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

  1. Changed23 schema fields changedv0.7.3
    • changedInput schema / properties / avgReviewCountMax / description
      Previous value: -"平均评论数上限——评论数越低意味着竞争越弱。"New value: +"Max average review count — lower means less competition."
    • changedInput schema / properties / avgReviewCountMin / description
      Previous value: -"平均评论数下限。"New value: +"Min average review count."
    • changedInput schema / properties / avgReviewRatingMin / description
      Previous value: -"平均评分下限(0-5)。"New value: +"Min average review rating (0-5)."
    • changedInput schema / properties / extraFilters / description
      Previous value: -"透传任意上游字段(如 sponsoredProductsPercentageT360Min、successfulLaunchesT360Max、avgBestSellerRankMax 等)。键名按 Pangolinfo 文档原样填写。"New value: +"Pass-through for any other upstream filter (e.g. sponsoredProductsPercentageT360Min, successfulLaunchesT360Max, avgBestSellerRankMax). Keys must match the upstream doc verbatim."
    • changedInput schema / properties / marketplaceId / description
      Previous value: -"Amazon 站点 ID(必填)。常见值:US、UK、DE、JP、FR、IT、ES、CA。默认 US。"New value: +"Amazon marketplace id (required). Common: US, UK, DE, JP, FR, IT, ES, CA. Defaults to US."
    • changedInput schema / properties / maximumPriceMax / description
      Previous value: -"利基内最高商品价格的上限。"New value: +"Upper bound on the niche's maximum product price."
    • changedInput schema / properties / minimumPriceMin / description
      Previous value: -"利基内最低商品价格的下限。"New value: +"Lower bound on the niche's minimum product price."
    • changedInput schema / properties / nicheId / description
      Previous value: -"传入单个利基 ID 时返回该利基的全维度深度报告(替代“详情接口”);不传则按筛选条件返回多个利基。Example: '8140a265-768d-4679-8bc2-994cb1c96f0b'(UUID 格式)。"New value: +"When set, returns the full deep report for that single niche (this endpoint doubles as the niche-detail endpoint). Omit to list multiple niches matching the filters. Example: '8140a265-768d-4679-8bc2-994cb1c96f0b' (UUID)."
    • changedInput schema / properties / nicheTitle / description
      Previous value: -"按关键词匹配利基标题。Examples: 'iphone 16 wallet case' / 'wireless earbuds for sports'。"New value: +"Keyword match against niche titles. Examples: 'iphone 16 wallet case' / 'wireless earbuds for sports'."
    • changedInput schema / properties / page / description
      Previous value: -"页码,从 1 开始。"New value: +"Page number, 1-based."
    • changedInput schema / properties / productCountMax / description
      Previous value: -"利基内商品数上限。"New value: +"Max product count in the niche."
    • changedInput schema / properties / productCountMin / description
      Previous value: -"利基内商品数下限。"New value: +"Min product count in the niche."
    • changedInput schema / properties / returnRateT360Max / description
      Previous value: -"近 360 天退货率上限(0-1)。"New value: +"Max return rate over 360 days (0-1)."
    • changedInput schema / properties / searchVolumeGrowthT90Max / description
      Previous value: -"近 90 天搜索量增长率上限。"New value: +"Max 90-day search-volume growth rate."
    • changedInput schema / properties / searchVolumeGrowthT90Min / description
      Previous value: -"近 90 天搜索量增长率下限(小数,0.1 = +10%)。"New value: +"Min 90-day search-volume growth rate (decimal, 0.1 = +10%)."
    • changedInput schema / properties / searchVolumeT360Max / description
      Previous value: -"近 360 天搜索量上限。"New value: +"Max search volume over last 360 days."
    • changedInput schema / properties / searchVolumeT360Min / description
      Previous value: -"近 360 天搜索量下限。"New value: +"Min search volume over last 360 days."
    • changedInput schema / properties / searchVolumeT90Max / description
      Previous value: -"近 90 天搜索量上限。"New value: +"Max search volume over last 90 days."
    • changedInput schema / properties / searchVolumeT90Min / description
      Previous value: -"近 90 天搜索量下限。"New value: +"Min search volume over last 90 days."
    • changedInput schema / properties / size / description
      Previous value: -"每页条数,上限 10(服务端硬限制),默认 3(小默认值避免 AI 上下文超限 — 需要更宽扫描时显式传 size=10)。"New value: +"Page size, max 10 (backend hard limit), default 3 (small default to keep responses under AI context limits — pass size=10 explicitly when you need a wider sweep)."
    • changedInput schema / properties / sortField / description
      Previous value: -"排序字段,支持任意响应字段名(如 'searchVolumeT90'、'avgProductPrice')。"New value: +"Sort field; any response field name is accepted (e.g. 'searchVolumeT90', 'avgProductPrice')."
    • changedInput schema / properties / sortOrder / description
      Previous value: -"排序顺序:'asc' 升序,'desc' 降序。"New value: +"Sort order: 'asc' or 'desc'."
    • changedInput schema / properties / top5ProductsClickShareT360Max / description
      Previous value: -"近 360 天前 5 商品点击份额上限(0-1)。值越低代表利基越分散、机会越大。"New value: +"Max top-5-products click share over 360 days (0-1). Lower = more fragmented niche, more opportunity."
  2. Changed2 schema fields changedv0.7.2
    • changedInput schema / properties / size / default
      Previous value: -10New value: +3
    • changedInput schema / properties / size / description
      Previous value: -"每页条数,上限 10(服务端硬限制)。"New value: +"每页条数,上限 10(服务端硬限制),默认 3(小默认值避免 AI 上下文超限 — 需要更宽扫描时显式传 size=10)。"
  3. First observedv0.2.1

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully discloses pagination behavior (page 1-based, size capped at 10, default 3, hasNext flag), cost (~1 point, ~5s), and filter range semantics (e.g., return rate as decimal 0-1).

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 with clear sections (use, don't use, returns, pair with, cost, tips), front-loaded with purpose, and every sentence adds value 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?

For a tool with 23 parameters, no output schema, and no annotations, the description is comprehensive: covers pagination, cost, return fields, filter examples, and pairings, making it fully actionable.

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 critical context: size default rationale (AI context limits), extraFilters pass-through, sortField accepting any response field, and a classic blue-ocean filter combo.

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 filters Amazon niches by 50+ commercial metrics, serves as a niche detail endpoint, and explicitly distinguishes from sibling tools like filter_categories and search_amazon.

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?

Provides explicit when-to-use examples (blue ocean, high search/low competition, niche detail) and when-not-to (full categories, products, plain keyword search) with alternative tool names.

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

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