Skip to main content
Glama

Customer reviews

list_reviews
Read-only

Reviews customers left on the site, by status (pending ones wait for approval). Approved reviews are published as schema on product pages and in llms.txt.

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": {
      "site": "<site>"
    },
    "name": "list_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug (e.g. "kopitiam-muar") or id
statusNopending
product_idNo

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?

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new lifecycle context — that approved reviews surface as schema on product pages and in llms.txt — but says nothing about result ordering, volume, or pagination for a listing call.

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

Conciseness5/5

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

Two compact sentences with zero filler, front-loading the resource and the status scoping before the downstream context. Every clause carries information an agent would not otherwise have.

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 three-parameter read with no output schema, the definition covers the conceptual model but leaves the product_id filter and result shape (fields returned, ordering, empty-state behavior) unaddressed. Adequate to start a call, but not fully self-sufficient.

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%: 'site' is documented, 'status' has an enum and default but no explanation, and 'product_id' is completely undocumented in both schema and description. The description lightly glosses the status meaning but never explains what product_id filters on, which is precisely the gap it should have filled at this coverage level.

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 resource (customer reviews left on the site) and scope (filterable by status), which clearly separates it from the mutating sibling moderate_review. It never uses an explicit verb like 'list' or 'retrieve', but the phrasing leaves little ambiguity about what the tool returns.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(pending ones wait for approval)' hints at the moderation workflow, letting an agent infer that approvals happen elsewhere (moderate_review). It never explicitly says when to call this versus moderate_review, nor does it mention prerequisites such as needing a site slug for a site the caller can access.

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