Judge.me MCP Server and API by Cotlet

Export reviews in Judge.me

judge_me_export_reviews

Read-onlyIdempotent

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-openWorld annotations, the description discloses that nothing is opened or mutated and that the payload is procedural guidance (screens, buttons, fields) plus a pointer to the browser tools. The one gap is that it does not say whether the guide is account-specific or how current the steps are beyond a single date stamp.

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 'opens nothing by itself' caveat before the API aside. The closing API/MCP note and the 'checked 23 Oct 2026' stamp are somewhat tangential, but they earn a small amount of place by heading off a dead-end lookup.

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?

With zero parameters and no output schema, the description carries the burden of explaining returns, and it does: a step-by-step how-to plus an explicit handoff to the cotlet_browser_* tools. Nothing an agent needs in order to call and use this 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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly adds no invented parameter discussion.

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 (export Judge.me reviews) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the export, and 'opens nothing by itself.' That resolves the ambiguity in the tool name, though the framing still leads with an action verb that only the second clause corrects.

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 to the follow-up path: use cotlet_browser_* tools in the user's Judge.me Cloud Browser after reading the guide. It also preempts the obvious alternative by noting Judge.me has no official MCP server. It does not say when to prefer this over sibling review tools like judge_me_list_reviews, but the workflow context is clear enough to act on.

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?