REVIEWS.io MCP Server and API by Cotlet

List reviews in REVIEWS.io

reviews_io_list_reviews

Read-onlyIdempotent

List reviews in the user's own REVIEWS.io account from ChatGPT, Claude or any AI agent. Returns how to do it in REVIEWS.io step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's REVIEWS.io Cloud Browser. REVIEWS.io's official API: REVIEWS.io has a REST API, but only on the Plus plan, and no official MCP server (checked 23 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reviews_io_list_reviews"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses the key non-obvious behavior: it performs no action and only returns screens/buttons/fields instructions, plus that REVIEWS.io's REST API is Plus-plan only and has no official MCP server. Return content is described at a high level but not in detail.

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?

Purpose is front-loaded, but the opening 'from ChatGPT, Claude or any AI agent' is filler and the trailing API/plan note with a 'checked 23 Oct 2026' date adds bulk with limited operational value. The core routing instruction is buried mid-sentence rather than given its own line.

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?

For a zero-parameter, no-output-schema tool, the description covers what it returns (step-by-step UI instructions) and what must happen next (browser tools), which is the necessary context. It could say more about what the instructions contain or any prerequisites (e.g. an open Cloud Browser session) before the follow-up call.

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

Parameters4/5

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

The input schema has zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. The description correctly implies the tool is parameterless by describing a fixed instructional output.

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 in the user's own REVIEWS.io account') and clarifies the tool itself is a how-to guide rather than an executor. It does not name any sibling tool (e.g. reviews_io_export_reviews) to differentiate scope, so it stops 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?

Explicitly routes the agent: this tool returns step-by-step instructions and 'opens nothing by itself', after which the agent should act via the cotlet_browser_* tools in the Cloud Browser. That is clear workflow guidance, though it gives no when-not-to-use condition or comparison against the other reviews_io_* siblings.

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

All REVIEWS.io MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?