Skip to main content
Glama
Pangolin-spg

Pangolinfo Amazon Data MCP

by Pangolin-spg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_category_paths

Resolve a batch of Amazon category IDs to full category paths for readable reporting. Use when you need category names instead of numeric IDs in reports or comparisons.

Instructions

[Amazon category breadcrumb resolver] Batch-resolve categoryId list to full paths (e.g. 'Electronics > Headphones > Over-Ear Headphones'). Use when: a report needs readable category context (not bare IDs); user has a list of numeric IDs and wants the names; multiple categories need labels for comparison. Don't use: for a single ID — most other tools already return browseNodeNamePath in their responses; for tree structure (use get_category_children). Returns: data.items[{ categoryId, categoryName, categoryNameCn, browseNodeNamePaths[], browseNodeNamePathCns[] }] — one row per input ID. Pair with: ↑ categoryIds from any prior step (filter_niches/filter_categories output, user-pasted ID list); ↓ usually presentation-only, downstream rarely depends on it. Cost: ~1 point/call, ~2s (cheaper than N single resolutions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoAmazon marketplace. Defaults to 'amz_us' (US).amz_us
categoryIdsYesCategory IDs to resolve full path for. Examples: ['2619526011'] (Appliances) / ['172282', '11965861'] (Electronics + Musical Instruments).
clientSourceNo调用来源标记。仅由 Pangolinfo Skill 传 skill；普通 MCP 调用省略即可。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does most of it: return shape, cost (~1 point/call, ~2s), and the efficiency claim vs N single resolutions. It stops short of permission/auth behavior, but for a read-only resolver the disclosed cost, latency, and return contract are substantial.

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?

Front-loads the purpose before labeled sections, and every section (Use when / Don't use / Returns / Pair with / Cost) earns its place. Slightly verbose with the arrow notation in 'Pair with', but nothing is wasted.

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?

No output schema exists, and the description compensates by spelling out the exact returned fields (categoryId, categoryName, browseNodeNamePath, etc.) and noting one row per input ID. An agent has everything needed to call and interpret the result.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented (including the categoryIds example and site default). The description adds no parameter-level semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: 'Batch-resolve categoryId list to full paths' with a concrete example output ('Electronics > Headphones > Over-Ear Headphones'). It explicitly distinguishes itself from get_category_children, so an agent can tell it apart from the closest sibling without opening either schema.

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' section names three triggering conditions (readable category context, list of numeric IDs needing names, labeling for comparison) and 'Don't use' rules out single-ID use and tree traversal, naming get_category_children as the alternative. Routing is fully specified.

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

Deploy Server

Other Tools