Property Finder MCP Server and API by Cotlet

Update agent in Property Finder

property_finder_update_agent

Read-onlyIdempotent

Update agent 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_update_agent"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description reinforces the readOnly annotation by stating that the tool 'opens nothing by itself' and returns instructions only. It adds useful behavioral context: the response contains step-by-step screens, buttons, and fields, and actual changes happen through separate browser tools. It does not describe authentication or account-state prerequisites beyond referring to the user's own account.

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 most important fact—that the tool returns instructions rather than performing an update—appears after an initial clause that sounds like a mutation. The mention of ChatGPT, Claude, or any AI agent is somewhat promotional, while the API-partner note is relevant but adds length. It is reasonably structured but not tightly front-loaded.

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 instructional tool with no output schema, the description gives enough context: what it returns, that it performs no browser action itself, and which sibling tools carry out the update. It could be more complete by stating any login or account prerequisites, but the core workflow is covered.

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, so the baseline is 4. There are no parameter semantics to explain, and the description appropriately focuses on the tool's output and workflow instead.

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 identifies a specific resource (agent in Property Finder) and clarifies that the tool actually returns step-by-step instructions rather than performing the update. This distinguishes it from the cotlet_browser_* tools, which perform the actions. The only weakness is that the leading verb 'Update' could initially suggest a mutation before the description corrects it.

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 clearly explains the workflow: use this tool to get Property Finder screens, buttons, and fields, then carry out the update with cotlet_browser_* tools in the user's Cloud Browser. It also notes that Property Finder's official API is only for approved software partners, implicitly steering brokers away from an API path. It does not explicitly state when not to use the tool, but the intended use is clear.

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?