REVIEWS.io MCP Server and API by Cotlet

Pause invitations in REVIEWS.io

reviews_io_pause_invitations

Read-onlyIdempotent

Pause invitations 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_pause_invitations"
  }
}

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 readOnlyHint/idempotent/non-destructive, and the description adds context the annotations cannot: that it returns 'screens, buttons, fields' as a guide and performs no action itself. The API note (REST only on Plus plan, no official MCP server) explains why browser automation is the follow-up path, which materially informs the agent's plan.

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-loads the action and the critical 'returns a guide, opens nothing' caveat in the first two sentences. The third sentence about REVIEWS.io's API availability is secondary and slightly dilutes focus, but it earns its place by justifying the browser-tool handoff.

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, read-only guide tool with no output schema, the description covers what it returns (step-by-step screens/buttons/fields), what it does not do (perform the change), and what to do next. Nothing an agent needs to invoke 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for an empty schema applies. The description correctly implies the only implicit input is the user's signed-in REVIEWS.io context.

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 ('Pause invitations') scoped to 'the user's own REVIEWS.io account', and crucially clarifies that the tool returns instructions rather than performing the action ('opens nothing by itself'). An agent can distinguish this from the write-oriented browser siblings without opening anything else.

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 an explicit two-phase workflow: call this to get the step-by-step procedure, then execute it with the named cotlet_browser_* tools in the Cloud Browser. It does not say when skipping the guide is acceptable (e.g. if the agent already knows the screens), so 'when-not' remains implicit.

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?