REVIEWS.io MCP Server and API by Cotlet

Export reviews in REVIEWS.io

reviews_io_export_reviews

Read-onlyIdempotent

Export 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_export_reviews"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world; the description adds the critical nuance that it performs no action ('opens nothing by itself') and returns static instructions, plus the plan-gated API caveat with a verification date. That goes well beyond what the annotations convey and prevents misreading 'export' as a live mutation.

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?

Front-loaded with the core behavior and the non-action caveat, with the API note last. Every sentence is relevant, though 'from ChatGPT, Claude or any AI agent' is slightly promotional filler that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter guide tool with annotations covering the safety profile and no output schema, the description supplies everything needed: what it returns, that it is inert, and the follow-up browser tools to use. Nothing an agent needs in order to call it correctly is missing.

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?

There are zero parameters, so there is nothing to document and the baseline is 4. The description correctly implies a no-input call and adds no misleading parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (export reviews in the user's own REVIEWS.io account) and then immediately disambiguates from a data-fetch sibling by saying it 'returns how to do it step by step' and 'opens nothing by itself'. An agent can tell this is an instruction/guide tool rather than a live data operation without opening any schema.

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 a clear workflow: use this for steps, then act with the cotlet_browser_* tools in the Cloud Browser. It also names the alternative path (official REST API, only on the Plus plan, no official MCP). Missing is an explicit 'when not to use this', but the context is strong.

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?