Skip to main content
Glama
Sign In

Crexi MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create listing in Crexi

crexi_create_listing
Read-onlyIdempotent

Create listing 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_create_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false; the description corroborates this by saying it opens nothing by itself and only returns instructions. The one gap is that it never states the user must already be signed in to Crexi in the Cloud Browser for the subsequent browser steps to work.

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 key constraint (returns a guide, opens nothing) is front-loaded in the first sentence, which is exactly right. The closing line about Crexi's API is slightly redundant in its phrasing ('Crexi's official API: Crexi has no public API') but still earns its place as justification.

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 guidance tool with no output schema, the description covers what is returned (screens, buttons, fields), what is not done (no browser opening), and the handoff path. Only the authentication precondition for the follow-on browser work is unstated.

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 schema declares zero properties, so there is nothing to disambiguate; the baseline applies. The description correctly leaves parameter interpretation out of scope rather than inventing inputs.

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 verb and resource (create a Crexi listing) but immediately corrects the expectation set by the name: the tool returns step-by-step guidance rather than performing the action. That distinction, plus naming the cotlet_browser_* tools as the actual executors, makes it unmistakable versus any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives both the when and the when-not: call this to get the Crexi walkthrough, then drive the UI with cotlet_browser_* because nothing is opened automatically. The absence of a public Crexi API is stated as the reason this indirection exists.

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