AestheticsPro by Cotlet

View Client/Lead Demographics in AestheticsPro

aestheticspro_view_client_lead_demographics

Read-onlyIdempotent

View Client/Lead Demographics 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_view_client_lead_demographics"
  }
}

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

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context beyond them: the tool "opens nothing by itself" and returns a step-by-step screen/button/field walkthrough, which is essential for an agent to predict the return value. The API-plan note also explains why a companion browser tool is required.

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 operational content is front-loaded in the first sentence, which is good structure. However, the trailing paragraph on AestheticsPro's $350/month Enterprise custom-API plan and documentation status is lengthy and only tangentially relevant to invoking this tool, and the opening phrase largely restates the title.

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?

For a zero-parameter, non-destructive tool with no output schema, the description covers the essentials: what it returns (screens, buttons, fields), what it does not do (open anything), and which tools complete the job. Minor gaps remain, such as what happens if the user is not signed in or lacks demographics permissions.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline applies. It correctly signals that no inputs are needed, and nothing in the text contradicts the empty schema.

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 ("View Client/Lead Demographics") and clarifies the crucial twist that it returns step-by-step instructions rather than the data itself. It does not, however, differentiate itself from close siblings such as aestheticspro_view_client_contact_details or aestheticspro_view_lead_list, so an agent must infer which view to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear follow-on path ("then do it with the cotlet_browser_* tools in the user's AestheticsPro Cloud Browser"), which is real usage guidance. But there are no explicit when/when-not conditions relative to the many other view_* siblings, so selection among alternatives is left to inference.

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?