Bayut MCP Server and API by Cotlet

Get listing performance in Bayut

bayut_get_listing_performance

Read-onlyIdempotent

Get listing performance in the user's own Bayut account from ChatGPT, Claude or any AI agent. Returns how to do it in Bayut step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bayut Cloud Browser. Bayut's official API: Bayut has no public developer API and publishes no API docs (checked 12 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": "bayut_get_listing_performance"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds the key behavioral fact that it returns instructions rather than opening pages or fetching data, though it doesn't discuss auth or rate limits.

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 resource, then clarifies that it returns steps and does not act, followed by the browser-tool handoff. Some filler such as 'from ChatGPT, Claude or any AI agent' and redundant 'Bayut's official API:' phrasing keep it from a 5.

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 discloses the return content (screens, buttons, fields), the non-action behavior, and the follow-up tool family. Minor prerequisites such as logged-in account state are not spelled out, but the core context is present.

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 has zero parameters and a 100% schema coverage baseline, so there is no parameter semantics to compensate for. The baseline for zero-param tools is 4.

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 it returns a step-by-step guide for getting listing performance in the user's Bayut account and explicitly says it opens nothing by itself, which distinguishes it from the cotlet_browser_* action tools. The name alone could mislead an agent into expecting performance data, but the description corrects that.

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?

Explains the intended sequence: call this for screens/buttons/fields, then execute those steps with cotlet_browser_* tools in the user's Bayut Cloud Browser, and notes Bayut has no public API. It lacks explicit when-not conditions or comparison to cotlet_app_guide, so it falls short of a 5.

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

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