Skip to main content
Glama

get_product_reviews

Read-onlyIdempotent

Get review statistics and the newest user reviews for the best-matching product. Takes the same filters as search_products. The summary covers all reviews; the review list is only the latest sample (default 10, max 20) and must not be presented as the overall opinion. Provides objective product data and user feedback for adults only; it does not provide guidance on circumventing age verification, purchase restrictions or other legal limits.

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": {
      "query": "<query>"
    },
    "name": "get_product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopNoOptional shop name.
limitNoNumber of reviews, 1-20. Default 10.
queryYesProduct name, brand, model or search keywords. Required.
countryNoOptional ISO 3166-1 alpha-2 country code of the shop location.
sort_byNolatest (default) or helpful.
languageNoOptional language code.
brand_nameNoOptional brand name.
model_nameNoOptional model name.
category_nameNoOptional product category name or code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description adds genuinely new behavioral context. It discloses that the summary aggregates all reviews while the list is only the latest sample (default 10, max 20) and explicitly forbids presenting that sample as the overall opinion. It also states the adults-only scope and that it will not help circumvent age verification or purchase restrictions, which is meaningful constraint disclosure beyond the annotations.

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?

Three sentences, front-loaded with the core purpose, then the sampling caveat, then the scope restriction. Each sentence carries distinct information, though the final policy sentence is somewhat long relative to its operational value. No filler or 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?

With nine parameters and no output schema, the description does well to explain that the response contains both aggregate statistics and a bounded review list. The one gap is that the shape and fields of the 'review statistics' summary are not described at all. Given annotations cover the read-only safety profile, the definition is otherwise sufficient to call the tool correctly.

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 every parameter (query, shop, country, limit, sort_by, language, brand_name, model_name, category_name) is already documented in the schema. The description only adds that the filter set mirrors search_products and repeats the limit default/max. Baseline 3 is appropriate since the schema carries the parameter semantics.

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?

States a specific verb and resource: 'Get review statistics and the newest user reviews for the best-matching product.' It distinguishes itself from search_products implicitly by noting it takes the same filters but returns reviews rather than product listings. It stops short of a crisp one-line contrast with the product-search sibling, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

'Takes the same filters as search_products' tells the agent this is the follow-up call once a product is identified, giving clear usage context. It also warns that the review list is a sample and must not be presented as the overall opinion, which shapes downstream use. It does not explicitly state when NOT to use it (e.g., for broad product discovery), so it falls short of a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources