Skip to main content
Glama
Pangolinfo Review Mining MCP

Pangolinfo Review Mining MCP

Official

get_product_reviews

Fetch paginated Amazon product reviews for a single ASIN with marketplace, star, media, and sort filters to support review mining and sentiment analysis.

Instructions

Fetch paginated Amazon product reviews for one ASIN via Pangolinfo, with the upstream billing (pointCost) reported verbatim. Billing: docs and measured calls show 5 credits/page; the upstream tool description currently states 10 credits/page — this tool reports pointCost as returned, it does not assert a rate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asin": "<asin>"
    },
    "name": "get_product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes10-character Amazon ASIN (case-insensitive).
siteNoAmazon marketplace. Defaults to amz_us.amz_us
sortByNoSort order: recent (default) or helpful.recent
mediaTypeNoall_contents (default) or media_reviews_only.all_contents
pageCountNoReview pages to fetch (~10 reviews per page). Each page bills credits on the Pangolinfo account — see billing notes.
filterByStarNoStar filter. 'critical' = negative reviews.all_stars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful billing behavior: 5 credits/page, the upstream 10-credit discrepancy, and that pointCost is reported verbatim rather than asserted. But it does not describe read-only semantics, rate limits, authentication needs, failure behavior, or return shape, leaving significant behavioral gaps.

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?

The description is front-loaded with the core action and then adds the billing caveat. It is appropriately sized and contains little waste, though the billing discrepancy explanation is fairly prominent relative to usage guidance.

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

Completeness3/5

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

The description covers purpose, pagination, and billing caveats, which is helpful for a six-parameter tool with no annotations. But with no output schema, it should say more about what the returned reviews look like beyond pointCost, and it does not provide enough context for an agent to understand the full response shape.

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 the schema already documents all six parameters, including enums and defaults. The description adds only a billing note relevant to pageCount and the 'one ASIN' scope, which is useful but minor beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Fetch paginated Amazon product reviews for one ASIN via Pangolinfo.' That is clear enough for an agent to know this is a raw review-fetching tool, especially against siblings like review_mining_report and review_sentiment_summary. However, it does not explicitly contrast itself with those analytical/reporting siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for fetching reviews for a single ASIN, but it gives no explicit when-to-use guidance, no when-not-to-use guidance, and no alternatives. An agent could infer it should use this for raw reviews rather than summaries, but that inference comes from the sibling names, not from the description.

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