Skip to main content
Glama

getReviews

Reviews for a product (id or slug). Display: reviews island → else short markdown. Call after getProduct before recommending purchase.

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": {
      "productId": "<productId>"
    },
    "name": "getReviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
pageSizeNo
productIdYesProduct id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole disclosure burden. It does reveal a rendering trait (reviews island first, otherwise short markdown), which is non-obvious, but says nothing about pagination defaults, result ordering, or what an empty review set looks like for a tool whose schema exposes page and pageSize.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded, which is good, but 'Display: reviews island → else short markdown' is telegraphic jargon that an agent cannot reliably act on. Every clause is relevant, yet the middle sentence trades clarity for brevity.

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?

For a simple three-parameter read tool with no output schema, the description covers the identifier, a rendering instruction, and a workflow cue. It leaves pagination behavior and the shape of the returned reviews unspecified, which is a real gap given the undocumented page parameters.

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

Parameters2/5

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

Schema coverage is only 33%: productId is documented in the schema and merely restated here as 'id or slug', while page and pageSize receive no explanation of defaults, limits, or effect. With the schema leaving two of three parameters undocumented, the description should compensate and does not.

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 the specific resource (reviews for a product) and the accepted identifier form (id or slug), which cleanly separates it from getProduct and submitReview. It does not name the sibling it is distinct from, keeping it 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 Guidelines4/5

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

Gives an explicit sequencing cue: call after getProduct and before recommending a purchase, which tells the agent exactly where this fits in a workflow. It offers no exclusions or alternatives (e.g., when reviews are not needed), so it stops short of full guidance.

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