Judge.me MCP Server and API by Cotlet

List reviews in Judge.me

judge_me_list_reviews

Read-onlyIdempotent

List reviews in the user's own Judge.me account from ChatGPT, Claude or any AI agent. Returns how to do it in Judge.me step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Judge.me Cloud Browser. Judge.me's official API: Judge.me has a REST API with a private API token and an OpenAPI file, but 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": "judge_me_list_reviews"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, non-destructive, and closed-world. The description adds useful context beyond annotations: it returns screen/button/field instructions, opens nothing itself, and notes there is no official MCP server. Auth requirements are only implicit.

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?

The description is somewhat run-on and includes an API availability note that, while informative, is not strictly needed to invoke the tool. The first sentence is misleading before the clarification in the second, reducing front-loaded clarity.

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 guide tool with no output schema, it adequately explains that it returns step-by-step instructions and does not perform the operation. It could say more about the exact return format or prerequisites, but it is mostly complete.

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 and schema description coverage is 100%, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly avoids doing so.

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

Purpose3/5

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

The description opens by saying it will 'List reviews,' but then clarifies that it actually returns step-by-step instructions and opens nothing itself, so the real purpose is a guide rather than a listing action. It does name the browser tools that perform the action, but the mismatch between name and behavior creates ambiguity with siblings like judge_me_export_reviews.

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?

It indicates this tool should be used to get steps and then cotlet_browser_* tools should perform the task, which is helpful routing guidance. However, it does not explicitly say when to prefer this over judge_me_export_reviews or other Judge.me siblings, and provides no exclusions.

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

All Judge.me 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?