AestheticsPro by Cotlet

Open the browser

cotlet_browser_open

Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In AestheticsPro it serves these actions: Search clients, Search leads, Add a client, View client contact details, Configure gender identity and pronouns, Apply client gender identity, View appointment calendar, View scheduling changes and availability, Create appointment, Modify appointment, View Book Now availability, Book an appointment online, Book through Client Portal, View appointment history, Configure Book Now, Configure Client Portal, Create staff calendar, Create room calendar, Add equipment, Map services to scheduling resources, Set appointment duration, Set staff schedule, Create schedule template, Notify client of an opening, Sync appointments to Google Calendar, Sync appointments to Apple Calendar, Schedule a virtual appointment, Configure appointment confirmations, Set appointment reminder timing, Choose reminder channel, Send automated appointment reminders, Read client texts, Send client text, Draft client communication with Kai, View lead list, Create lead, Segment leads, Assign lead, View Client/Lead Demographics, Export contacts to Constant Contact, View communication dashboard, View outreach calendar, Create email template, Create SMS template, Draft outreach campaign with AI, Customize outreach campaign, Create text list, Send SMS blast, Create email list, Schedule E-Blast, Enable Touchpoints, Draft client journey, Configure client journey, Activate client journey, Adjust scheduled outreach, View email and SMS engagement, View appointment reports, Create staff announcement, View client appointment history, Send review request.

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": "cotlet_browser_open"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	Leave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
`url`	No	A public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the description's job is to add context, and it does: the user is signed in, existing tabs are preserved, and the call answers with the visible page elements and text. That return-shape note is valuable because there is no output schema. It does not cover failure modes (e.g., browser fails to launch, private URL rejected) or session lifetime, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are tight and front-loaded, but the long enumeration of AestheticsPro actions dominates the text and adds no invocation guidance for this specific tool. It inflates token cost and invites misreading of scope, which is the opposite of earning its place.

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 two-optional-parameter browser-launch tool with no output schema, the description covers the essentials: call order, tab placement, signed-in session context, and what the follow-up response contains. Error behavior and how this pairs with cotlet_browser_close are the notable omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema already explains that `app` should normally be omitted and gives the URI format for `url`. The description adds a behavioral note about where the URL lands (existing tab vs. new tab) but no additional syntax or constraint detail. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 opening sentence gives a specific verb and resource: it starts the user's Cloud Browser (real Chrome, signed in) and opens a URL, with 'Call it first' as an ordering rule. That cleanly separates it from cotlet_browser_navigate or cotlet_browser_tabs. The trailing catalogue of ~70 AestheticsPro actions muddies purpose, since it implies this tool performs actions like 'Send SMS blast' or 'Create lead' when it only opens a page.

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?

'Call it first' is an explicit sequencing directive that tells the agent when to reach for this tool relative to the other browser tools. It also explains the tab behavior so the agent knows an already-open tab is reused. It does not explicitly say when to prefer cotlet_browser_navigate instead, so it stops short of full routing guidance.

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?