Houzz Pro MCP Server and API by Cotlet

Create project in Houzz Pro

houzz_pro_create_project

Read-onlyIdempotent

Create project 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_create_project"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), it explains the crucial behavioral fact that nothing is opened or mutated and that a separate browser tool must carry out the steps. It also explains why this pattern exists (no public Houzz Pro API for leads/projects/estimates/invoices), which is useful operational context. The return structure is described only loosely as 'screens, buttons, fields'.

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?

Three sentences, front-loaded with the core behavior and the browser-tool handoff, with the API note placed last as justification. The phrase 'from ChatGPT, Claude or any AI agent' is mild filler, but overall there is little waste.

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?

With no input parameters and no output schema, the description carries the burden of explaining the return value, and it does so at a high level (step-by-step instructions with screens, buttons, fields). More detail on the exact return shape would help, but an agent knows what it will get and what to do next.

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 doesn't need to explain any inputs, and it correctly implies the target account is the user's own Houzz Pro account rather than a parameter-supplied one.

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 specifies what the tool returns (a step-by-step guide with screens, buttons, fields) and explicitly says it opens nothing by itself, which disambiguates it from the cotlet_browser_* execution tools. The remaining ambiguity comes from the name 'create_project' implying an action the description then walks back, but the text itself is clear about the guidance-only role.

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 concrete workflow: call this first to get the steps, then perform them with cotlet_browser_* tools in the Houzz Pro Cloud Browser. It doesn't name when-not-to-use cases or contrast with the other houzz_pro_* siblings, but the sequencing guidance is clear enough for an agent to act on.

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?