AestheticsPro by Cotlet

Create SMS template in AestheticsPro

aestheticspro_create_sms_template

Read-onlyIdempotent

Create SMS template 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_create_sms_template"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real context beyond the annotations by declaring "opens nothing by itself" (reinforcing readOnlyHint) and specifying the return content as screens, buttons, and fields to follow. The API-availability note explains why this is a guidance tool. It does not describe failure modes or what happens if the Cloud Browser session is unavailable.

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?

Purpose and the guide/hand-off behavior are front-loaded, which is good. The closing API paragraph, including the "$350 a month Enterprise plan" pricing detail and the checked-date, is longer than needed to make the point that no public API exists.

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 parameters, no output schema, and readOnly/idempotent annotations already covering safety, the description supplies what matters: what is returned and what to do next. Minor gaps remain around expected input source and the Cloud Browser prerequisite.

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 the schema baseline applies and there is no parameter semantics to compensate for. The description does not say where the SMS template content itself comes from (presumably the conversation), which is the one semantic gap for a zero-arg tool.

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 ("Create SMS template") scoped to "the user's own AestheticsPro account," and immediately clarifies the real behavior: it returns instructions rather than performing the creation. It does not explicitly distinguish itself from close siblings like aestheticspro_create_email_template or aestheticspro_create_schedule_template, though the SMS specificity in the name carries most of that load.

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 workflow: get the step-by-step guide here, then execute it with the cotlet_browser_* tools in the AestheticsPro Cloud Browser. It also explains why there is no API path, which pre-empts an agent trying one. It stops short of explicit when-not-to-use or exclusions versus the email/schedule template siblings.

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?