Houzz Pro MCP Server and API by Cotlet

List leads in Houzz Pro

houzz_pro_list_leads

Read-onlyIdempotent

List leads in the user's own Houzz Pro account from ChatGPT, Claude or any AI agent. Returns how to do it in Houzz Pro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Houzz Pro Cloud Browser. Houzz Pro's official API: Houzz Pro has no public API for leads, projects, estimates or invoices (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": "houzz_pro_list_leads"
  }
}

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?

Annotations already declare it read-only, idempotent and non-destructive, and the description adds genuinely new context: it 'opens nothing by itself' and only returns screens/buttons/fields. The note that Houzz Pro exposes no public API for leads, projects, estimates or invoices explains why the browser workflow exists, which is useful behavioral framing.

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 message is front-loaded, but the opening clause aimed at 'ChatGPT, Claude or any AI agent' is promotional filler, and the API sentence repeats 'Houzz Pro' awkwardly. A specific date ('checked 11 Oct 2026') adds length without helping the agent decide or act.

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?

No output schema exists, and the description compensates by saying the return is a step-by-step walkthrough with screens, buttons and fields. Combined with the no-side-effects statement and the browser-tool handoff, an agent has enough to call it and use the result correctly; only the exact return structure remains slightly vague.

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?

With zero parameters and full schema coverage there is nothing parameter-level to explain, so the baseline applies. The description correctly does not invent parameter semantics.

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 names a specific verb and resource (list leads in the user's Houzz Pro account) and immediately clarifies the crucial twist that the tool returns step-by-step instructions rather than data. The name/title ('List leads') slightly oversells an executor role, but the second sentence removes that ambiguity.

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 explicitly states the follow-on path: get the walkthrough here, then perform it with cotlet_browser_* tools in the Houzz Pro Cloud Browser. That routes the agent away from expecting a direct data fetch, though it does not state when this tool should be skipped or what a preferred alternative would be.

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

All Houzz Pro 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?