Skip to main content
Glama
pangolinfo

PangolinFo Amazon Ad Tracker & Review Intelligence

Official
by pangolinfo

filter_niches

Filter Amazon niches by 50+ metrics to uncover high-opportunity markets with low competition and rising search volume. Access comprehensive reports for individual niches.

Instructions

[Amazon 利基筛选] 按 50+ 维指标筛选 Amazon Niche(比类目更细的"消费需求簇"),或当作"niche 详情"接口取单个 niche 完整深度报告。 Use when: 用户说"找蓝海""高搜索量低竞争的利基""增长快的小众市场""niche 选品""为这个 niche 出详细报告";GTM 选品 SOP 的核心筛选步骤;要某个 niche 的费用结构 / 品牌年龄 / 新品上架趋势等深度指标。 Don't use: 想筛整类目(用 filter_categories);想看 niche 下的具体商品(用 list_category_products 配合 categoryId,niche 自带的样品 ASIN 只有 1 个 referenceAsin);只想要广义关键词搜索(用 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, 各项费用 T365 ... 100+ 字段 }] + data.items.pagination.{ total, page, size, hasNext }。翻页: 用 page 参数(默认 1,从 1 开始,size 上限 10);pagination.hasNext=true 表示还有下一页,hasNext=false 表示已到底。 Pair with: ↑ 必填 marketplaceId(默认 US);nicheTitle 关键词过滤,nicheId 单 niche 详情;↓ 拿到 referenceAsin 后喂 get_amazon_product 看代表品;niche 不直接关联 categoryId,需要二次推断。 Cost: ~1 积点/次, ~5s。 Tips: size 上限 10;50+ 长尾筛选字段走 extraFilters 透传;典型蓝海过滤组合 = searchVolumeT90Min 高 + top5ProductsClickShareT360Max 低 + productCountMax 中 + searchVolumeGrowthT90Min > 0。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketplaceIdNoAmazon 站点 ID(必填)。常见值:US、UK、DE、JP、FR、IT、ES、CA。默认 US。US
nicheIdNo传入单个利基 ID 时返回该利基的全维度深度报告(替代“详情接口”);不传则按筛选条件返回多个利基。Example: '8140a265-768d-4679-8bc2-994cb1c96f0b'(UUID 格式)。
nicheTitleNo按关键词匹配利基标题。Examples: 'iphone 16 wallet case' / 'wireless earbuds for sports'。
pageNo页码,从 1 开始。
sizeNo每页条数,上限 10(服务端硬限制)。
sortFieldNo排序字段,支持任意响应字段名(如 'searchVolumeT90'、'avgProductPrice')。
sortOrderNo排序顺序:'asc' 升序,'desc' 降序。
searchVolumeT90MinNo近 90 天搜索量下限。
searchVolumeT90MaxNo近 90 天搜索量上限。
searchVolumeT360MinNo近 360 天搜索量下限。
searchVolumeT360MaxNo近 360 天搜索量上限。
searchVolumeGrowthT90MinNo近 90 天搜索量增长率下限(小数,0.1 = +10%)。
searchVolumeGrowthT90MaxNo近 90 天搜索量增长率上限。
minimumPriceMinNo利基内最低商品价格的下限。
maximumPriceMaxNo利基内最高商品价格的上限。
productCountMinNo利基内商品数下限。
productCountMaxNo利基内商品数上限。
avgReviewCountMinNo平均评论数下限。
avgReviewCountMaxNo平均评论数上限——评论数越低意味着竞争越弱。
avgReviewRatingMinNo平均评分下限(0-5)。
top5ProductsClickShareT360MaxNo近 360 天前 5 商品点击份额上限(0-1)。值越低代表利基越分散、机会越大。
returnRateT360MaxNo近 360 天退货率上限(0-1)。
extraFiltersNo透传任意上游字段(如 sponsoredProductsPercentageT360Min、successfulLaunchesT360Max、avgBestSellerRankMax 等)。键名按 Pangolinfo 文档原样填写。
Behavior4/5

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

No annotations provided; description compensates by disclosing cost (~1 point, ~5s), pagination logic, size limit (max 10), and typical filter combination for blue ocean niches. No contradiction.

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 relatively long but well-structured: front-loads purpose, then usage, returns, pairing, cost, tips. Every section adds value without unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 23 parameters with full schema coverage and no output schema, description details return fields (100+ fields) and pagination. Also provides pairing with other tools. Complete for complex tool.

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% (all 23 parameters described). Description adds meaning beyond schema: nicheId for single detail, extraFilters for long-tail fields, pagination details, and typical filter combo. Baseline 3 plus extra value.

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?

Description clearly states tool for filtering Amazon Niches by 50+ metrics or retrieving single niche detail. Uses specific verb-resource combo '筛选' (filter) and differentiates from siblings 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?

Explicitly lists when to use (e.g., '找蓝海', '高搜索量低竞争的利基') and when not to (e.g., filter categories, view specific products). Names alternatives: filter_categories, list_category_products, search_amazon.

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