Skip to main content
Glama

Pagetool

List reviews and the current reviewable versions

list_reviews
Read-onlyIdempotent

For one site: whether publishing with the operator token needs a review (enforced), the current draft and staged versions (what record_review must name), and the reviews recorded so far, newest first.

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_key": "<site_key>"
    },
    "name": "list_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyYesThe site whose reviews and current reviewable versions to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely new context beyond them: ordering ('newest first'), the inclusion of an enforcement flag, and the fact that current draft and staged versions are returned as part of the same call.

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?

One sentence that is front-loaded with the scope ('For one site') and then enumerates the payload. The stacked parentheticals make it slightly dense, but no sentence is wasted.

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 no output schema, the description carries the burden of describing return values, and it does so adequately by naming the three components and the ordering. Minor gaps remain: nothing about pagination or limits on the reviews list, and no explicit statement of what the versions payload contains.

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?

There is a single parameter with 100% schema description coverage that already explains it is the site whose reviews and versions are listed. The description restates that scoping ('For one site') without adding format, validation, or edge-case 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?

The description names a specific verb+resource ('list' reviews) and enumerates the three things returned: the review-enforcement flag, the current draft/staged versions, and the recorded reviews. It also implies the link to record_review, though it doesn't explicitly differentiate itself from list_versions.

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 '(what record_review must name)' suggests this tool is the discovery step before recording a review. There is no explicit when-to-use or when-not-to-use guidance, and no mention of when list_versions would be the better choice.

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