AestheticsPro by Cotlet

Create lead in AestheticsPro

aestheticspro_create_lead

Read-onlyIdempotent

Create lead in the user's own AestheticsPro account from ChatGPT, Claude or any AI agent. Returns how to do it in AestheticsPro step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's AestheticsPro Cloud Browser. AestheticsPro's official API: AestheticsPro offers "Custom API solutions" only as custom work on its $350 a month Enterprise plan, arranged with AestheticsPro, and publishes no public API documentation or self-serve API key page (checked 11 Nov 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": "aestheticspro_create_lead"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/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; the description reinforces and explains them by stating the tool 'opens nothing by itself', so the readOnly annotation is not merely consistent but justified. The API-availability note explains why browser automation is the required follow-up path, which is genuine context an agent cannot get from structured fields.

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 first two sentences are front-loaded and high value. The final sentence is bloated with vendor commercial detail ('$350 a month Enterprise plan', 'checked 11 Nov 2026') that does not help an agent invoke the tool; the operative point, that no public API exists, could be stated in a fraction of the words.

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 parameters, no output schema and rich annotations, the description covers everything needed: what it returns (step-by-step screens, buttons, fields), that it performs no mutation, and which tool family completes the task. It does not describe what happens if the user's browser session is not connected, which is the one operational gap.

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 correctly implies no input is needed: the agent simply asks for the procedure and the lead details are presumably carried in conversation. Nothing is left ambiguous about what must be supplied.

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 action-object pair (create lead in AestheticsPro) but immediately reframes it: the tool returns step-by-step screens/buttons/fields instructions rather than creating anything. That reframing is essential and well stated, though the tool name and description pull in slightly different directions, requiring the agent to read past the first clause to understand it is a guidance tool.

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 explicit routing: use this to get the procedure, then execute it with the cotlet_browser_* tools in the AestheticsPro Cloud Browser. That is a clear when-and-with-what. It lacks an explicit exclusion such as 'do not use when the user only wants to view leads', so alternatives are implied rather than enumerated.

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

All AestheticsPro 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?