Skip to main content
Glama

AestheticsPro by Cotlet

Configure gender identity and pronouns in AestheticsPro

aestheticspro_configure_gender_identity_and_pronouns
Read-onlyIdempotent

Configure gender identity and pronouns 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_configure_gender_identity_and_pronouns"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The claim 'opens nothing by itself' is consistent with readOnlyHint=true and destructiveHint=false and adds useful clarity about the no-op nature of the call. It also explains the return shape (step-by-step screens, buttons, fields) and why browser automation rather than an API is required; the Enterprise-plan/API note is extra context but reinforces the same point.

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 core is front-loaded and efficient, but the closing sentence quoting the vendor's $350/month Enterprise plan and a 'checked 11 Nov 2026' date is lengthy vendor detail that does little to help an agent invoke this specific tool. The definition would lose nothing if that were trimmed.

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, no output schema, and rich annotations already covering safety and idempotency, the description supplies everything needed: what it returns, that it changes nothing, and which tools to use afterward. Only the return-format granularity could be slightly tighter.

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 and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline for a 0-parameter tool is 4.

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 verb and resource (configure gender identity and pronouns) and constrains scope to 'the user's own AestheticsPro account', which implicitly separates it from a sibling like aestheticspro_apply_client_gender_identity. It stops short of naming that sibling, so the differentiation is inferred rather than stated.

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 clearly describes the two-step workflow: this tool only returns step-by-step screens/buttons/fields, and the actual change must be made with the cotlet_browser_* tools in the Cloud Browser. It does not state explicit exclusions (e.g., when to use the client-applying sibling instead), but the operating context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources