AestheticsPro by Cotlet

Set appointment duration in AestheticsPro

aestheticspro_set_appointment_duration

Read-onlyIdempotent

Set appointment duration 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_set_appointment_duration"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/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 openWorldHint=false, and the description is consistent with them by stating the tool "opens nothing by itself." It adds value beyond annotations by specifying the return content (step-by-step screens, buttons, fields) and by explaining why browser automation is required (no public AestheticsPro API, only $350/mo custom Enterprise work).

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?

The first two sentences are tight and front-load purpose, return content, and the handoff to cotlet_browser_* tools. The closing sentence about AestheticsPro's Enterprise API pricing and the check date is longer than needed for invocation decisions, but it does justify the browser-based workflow.

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-executing guidance tool with annotations and no output schema, the description covers what the tool does, what it returns, what it does not do, and what to do next. Only minor gaps remain, such as roughly what form the returned instructions take or how to supply the target duration value.

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 parameter semantics to document; the description correctly does not invent any. Baseline for a parameterless tool applies.

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 uses a specific verb+resource ("Set appointment duration in ... AestheticsPro") and immediately qualifies the mechanism: it returns step-by-step instructions rather than performing the change. That distinguishes it from action-performing siblings like aestheticspro_create_appointment, though the name/verb "set" slightly overstates what the tool actually does until the second sentence clarifies.

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 a clear usage sequence: call this tool to get the screens/buttons/fields, then execute with the cotlet_browser_* tools. It also states the tool targets "the user's own AestheticsPro account" so scope is clear. It stops short of explicitly saying when NOT to use it (e.g., when a direct API path exists), but the workflow guidance is practical.

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?