Skip to main content
Glama

List reviews

list_reviews
Read-onlyIdempotent

List reviews for a live FastDrop product by its slug. Returns the average rating, total count, and individual reviews (rating, body, author, date). Unauthenticated - available to any agent.

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

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug
limitNoMax results, 1-50, default 20

Output Schema

NameRequiredDescriptionDefault
slugYes
countYes
averageYes
reviewsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds the genuinely useful auth fact ("Unauthenticated - available to any agent") but says nothing about pagination behavior or what happens when the slug is not a live product, which are the meaningful unknowns left.

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?

Two tight sentences with the action and scope front-loaded and zero filler. The parenthetical field list (rating, body, author, date) mildly duplicates the output schema, but it is short enough not to be wasteful.

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 an output schema present, the description needn't detail return values, and annotations cover the safety profile; the auth note fills the main remaining gap. The only omission is guidance on using limit for pagination on large review sets, a minor gap for a low-complexity two-parameter tool.

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 both parameters (slug, limit 1-50 default 20) are already documented in the schema. The description names slug but adds no semantics beyond the schema for limit, so the baseline 3 applies.

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 ("List reviews") scoped to "a live FastDrop product by its slug", which clearly separates it from sibling list_comments and get_product. It stops short of explicitly naming which sibling to prefer when the agent wants aggregated ratings versus raw review text.

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?

The scope word "live" implies this only works for launched products, which is useful usage context, but there is no explicit when-to-use or when-not-to-use guidance against list_comments or get_product. The agent must infer that this is the review-retrieval path.

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