Skip to main content
Glama
pangolinfo

PangolinFo Amazon Ad Tracker & Review Intelligence

Official
by pangolinfo

search_categories

Search Amazon categories by keyword to retrieve matching nodes with browseNodeIds for ad tracking and product analysis.

Instructions

[Amazon 类目搜索] 用关键词(中英文均可)匹配 Amazon 类目树,返回候选类目节点。 Use when: 用户给的是关键词而非类目 ID,下游需要 categoryId / browseNodeId(如想跑 filter_niches / filter_categories / list_category_products / list_bestsellers slug 推测);想知道某个商品概念在 Amazon 类目体系里挂在哪。 Don't use: 已经有 categoryId/nodeId(直接用 get_category_paths 取面包屑或下游 filter);想树状下钻看子类目(用 get_category_children)。 Returns: data.items.data[{ browseNodeId, browseNodeIdPath, browseNodeName, browseNodeNameCn, browseNodeNamePath, browseNodeNamePathCn, parentBrowseNodeIdPath, productType, sellable, hasChild }] + pagination。 Pair with: ↓ 拿到 browseNodeId 后喂 list_category_products / list_bestsellers (用 path 推 slug) / filter_niches / filter_categories;↓ 喂 get_category_children 继续下钻;↓ 喂 get_category_paths 取面包屑。 Cost: ~1 积点/次, ~3s。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes类目名称关键词(中英文均可)。Examples: 'headphones' / 'kitchen knives' / '无线耳机' / 'wireless earbuds'。
siteNo搜索的 Amazon 站点。默认 amz_us(美国站)。amz_us
Behavior4/5

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

No annotations provided, but description discloses cost (~1 credit, ~3s), return structure, and read-only nature. Could mention rate limits or idempotency, but adequate.

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?

Well-structured with bullet points and sections, front-loaded purpose. Slightly verbose with Chinese mixed in, but efficient overall.

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?

Covers purpose, usage, return structure, cost, pairing, and alternatives. No output schema but description compensates fully.

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% and descriptions are provided, but the tool description adds extra context like response structure and usage examples, going beyond schema.

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 searches Amazon category tree by keyword and returns candidate category nodes. It distinguishes from siblings like get_category_paths and get_category_children.

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 provide clear guidance on when to use this tool vs alternatives, including pairing with other tools.

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