AestheticsPro by Cotlet

Add a client in AestheticsPro

aestheticspro_add_a_client

Read-onlyIdempotent

Add a client 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_add_a_client"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations by stating the tool 'opens nothing by itself' (confirming the readOnly behavior), describing exactly what is returned (screens, buttons, fields), naming the mechanism needed to actually perform the action, and explaining why (no public AestheticsPro API, only a $350/mo Enterprise custom option). This is unusually rich disclosure for a zero-param tool.

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?

Front-loaded with the action and the crucial 'returns how to do it' caveat before the execution pointer. The API/Enterprise-plan sentence is longer than strictly necessary but earns its place by explaining why browser automation is the only path.

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 zero parameters and no output schema, the description still tells the agent what the response contains (step-by-step screens, buttons, fields) and what to do next. Only minor gaps remain, such as what happens if the user has no connected AestheticsPro account.

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 no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly implies no input is needed because the account is the user's own connected account.

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?

States a specific verb and resource ('Add a client in ... AestheticsPro') and immediately clarifies that this tool returns instructions rather than performing the action. That distinction is the key differentiator, though it doesn't name specific siblings such as project-creation tools it might be confused with.

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?

Explicitly routes the agent: use this to get step-by-step guidance, then execute with the cotlet_browser_* tools in the Cloud Browser. It gives clear positive guidance and a named follow-on, but does not state when not to use it or how it differs from other how-to tools in the catalog.

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?