AestheticsPro by Cotlet

Customize outreach campaign in AestheticsPro

aestheticspro_customize_outreach_campaign

Read-onlyIdempotent

Customize outreach campaign 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_customize_outreach_campaign"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial context beyond annotations by clarifying that the tool opens nothing by itself and returns step-by-step instructions for the user to follow in the browser. It also discloses the lack of a public AestheticsPro API, which explains why browser automation is required. This is fully consistent with readOnlyHint=true and destructiveHint=false.

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 description is front-loaded with purpose and behavior, then follows with API context. The API sentence is detailed, including pricing and date checked, but it earns its place by justifying the browser-tool workflow and preventing attempts to use an unavailable API.

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

Completeness5/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 guidance tool with no output schema, the description is complete enough: it states what the tool returns, that it performs no action itself, and how to proceed with execution. The added API context further explains the tool's role.

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 has zero parameters, so the parameter semantics baseline is 4. The description does not need to explain parameters, and the schema coverage is complete.

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 states a specific resource and scope: customizing an outreach campaign in the user's own AestheticsPro account. It clarifies that the tool returns step-by-step instructions rather than performing the action, but the tool name and title remain action-oriented and do not explicitly differentiate it from sibling campaign tools like draft_outreach_campaign_with_ai or adjust_scheduled_outreach.

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?

The description gives clear usage context: use this tool to get step-by-step guidance, then execute with the cotlet_browser_* tools. It does not explicitly state when to use this versus sibling AestheticsPro campaign tools, but the alternative execution path is named and the guidance context is clear.

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?