Zoopla MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Zoopla it covers these actions: List my listings, Update listing, Reply to lead, Get listing stats.

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": "cotlet_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Zoopla.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds context those annotations cannot convey: the call is free, consumes no browser session, works for any web app, and degrades to a general method outside the catalog, plus the concrete Zoopla action coverage.

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?

The purpose is front-loaded in the opening clause, and the operational constraints (call timing, no session, catalog fallback) follow in short sentences. The long first sentence packs many enumerated items and could be split, but every element listed corresponds to real guidance content rather than filler.

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 no output schema, the description carries the burden of explaining what comes back, and it does so by enumerating the guidance sections (browser choice, sign-in link, method, screens/menus/actions, notes, dedicated tools). Combined with the timing rule and catalog fallback, an agent has everything needed to call it correctly before a browser step.

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

Parameters3/5

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

Schema description coverage is 100%, and the description adds little about the two parameters themselves beyond restating the app/slug concept and task intent already documented in the properties (including the Zoopla default). The enumerated guidance content describes return information rather than parameter meaning, so the baseline 3 applies.

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?

The description states a specific resource and verb: retrieve guidance for working in a given web app via the Cloud Browser. It enumerates what the guidance contains (browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, dedicated tools) and explicitly separates itself from the browser action siblings by noting it needs 'no browser session' and must be called before the first browser step.

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?

It gives a clear trigger ('Call it before the first browser step in an app') and a fallback rule for apps outside Cotlet's catalog ('gets the general method'). It stops short of naming a specific alternative sibling such as cotlet_apps for catalog discovery, but the when-to-use condition is unambiguous.

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

All Zoopla 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?