Skip to main content
Glama
Sign In

Crexi MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get listing analytics in Crexi

crexi_get_listing_analytics
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: it returns procedural guidance, performs no navigation, and requires a follow-up browser call. The note that Crexi has no public API (checked 11 Oct 2026) further explains why this is a guide and not an API wrapper.

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 core purpose and workflow are front-loaded, but the 'from ChatGPT, Claude or any AI agent' phrasing and the dated API-verification note are marketing/noise that do not help an agent decide or invoke. The sentence structure is otherwise serviceable.

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, read-only guide tool with no output schema, the description covers what it returns and how to act on it. The only remaining gap is not naming the sibling guide tool as an alternative, which is minor for this complexity level.

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. The description correctly implies no input is needed and instead specifies what the returned payload contains (screens, buttons, fields), leaving no parameter ambiguity.

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?

The description gives a specific verb and resource (get listing analytics in the user's Crexi account) and immediately clarifies that what is actually returned is a step-by-step how-to rather than analytics data, which disambiguates the slightly misleading tool name. It does not explicitly differentiate from siblings such as crexi_get_comps or cotlet_app_guide, so it falls short of a 5.

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 states a clear two-step workflow: call this to get screens/buttons/fields, then execute with the cotlet_browser_* tools in the user's Crexi Cloud Browser, and it explicitly notes the tool 'opens nothing by itself.' No when-not-to-use condition or comparison to cotlet_app_guide is given, keeping it below a 5.

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

All Crexi MCP Server and API by Cotlet toolsInspect
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