Property Finder MCP Server and API by Cotlet

Publish listing in Property Finder

property_finder_publish_listing

Read-onlyIdempotent

Publish listing in the user's own Property Finder account from ChatGPT, Claude or any AI agent. Returns how to do it in Property Finder step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Property Finder Cloud Browser. Property Finder's official API: Property Finder has an API, but only for software partners it approves through the PF Developer Network, not for brokers directly (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": "property_finder_publish_listing"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 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=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself'. It also adds genuinely new context by explaining why no API path exists (partner-only PF Developer Network), which prevents an agent from looking for an API alternative.

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 core purpose and the 'opens nothing by itself' caveat are front-loaded in the first clause, and the API note is placed last. Some wording is filler, notably 'from ChatGPT, Claude or any AI agent' and the '(checked 11 Oct 2026)' date stamp, which do not help an agent decide or invoke.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should explain how the tool knows which listing to publish and whether a Cloud Browser session must be open first; neither is addressed. It does describe the shape of the return value (screens, buttons, fields), which covers part of the gap, but an agent could still call it without knowing the required session state.

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 there is no parameter meaning for the description to add; the baseline for a parameterless tool applies. Nothing in the description misdescribes 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 resource (a Property Finder listing) and clarifies the real behavior: it returns step-by-step instructions rather than performing the publish. It explicitly distinguishes itself from the cotlet_browser_* tools that carry out the actual work, so an agent can tell the two apart without opening a schema.

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 usage sequence: call this first to get the screens/buttons/fields, then execute with cotlet_browser_* in the user's Cloud Browser. It does not mention the sibling property_finder_unpublish_listing or state any preconditions such as needing an open browser session, so the guidance is clear but not exhaustive.

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

All Property Finder 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?