AestheticsPro by Cotlet

Draft client journey in AestheticsPro

aestheticspro_draft_client_journey

Read-onlyIdempotent

Draft client journey 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_draft_client_journey"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Adds real context beyond the annotations: the return value is procedural guidance (screens, buttons, fields), the tool performs no UI action, and follow-up happens through browser tools. The API note explains why a browser route is required, which is useful, but it spends a lot of the description on vendor plan pricing rather than on prerequisites like whether an authenticated Cloud Browser session must already exist. Annotations already cover the read-only, idempotent, non-destructive profile.

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?

Purpose is front-loaded, followed by behavior and the execution path, which is the right ordering. The final sentence on Enterprise pricing is longer than needed to make its point and could be compressed to 'no public API; browser automation required.'

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with no output schema, the definition covers what is returned and how to act on it. Gaps remain around session/auth prerequisites for the Cloud Browser step and whether the returned steps are version- or plan-specific, which matter for an agent that must chain into browser tools.

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 there is no semantic burden on the description and the empty schema is fully consistent with the definition.

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 ('Draft client journey') plus the account context, and clarifies the deliverable is step-by-step instructions rather than a performed action. It does not explicitly contrast itself with close siblings such as aestheticspro_activate_client_journey or aestheticspro_configure_client_journey, so the agent must infer that 'draft' is the precursor stage.

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?

Gives a clear operative sequence: call this to get the steps, then execute them with cotlet_browser_* tools in the Cloud Browser, and explicitly notes the tool 'opens nothing by itself.' It stops short of naming when to choose activate/configure instead, though the drafting-versus-executing split is strongly implied.

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?