Gladly MCP Server and API 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 Gladly it serves these actions: List conversations, Search customers, Reply to customer, Add note, Apply topics, Assign conversation, Close conversation, Create task.

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 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description explains the auth context (already signed in), tab-reuse so the user's tabs are preserved, and that the page snapshot is returned with consistent element numbering. Minor tension: 'Starts' a browser is a side effect while readOnlyHint=true, though nothing user-owned is modified, so it is not a contradiction.

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 opening sentence front-loads the essential action and sequencing, and each later sentence adds real information about tab handling and return payload. The trailing Gladly action list is useful context but slightly list-like padding for a tool whose core behavior is already stated.

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 output schema, the description correctly explains what comes back (visible elements and text with matching numbers), which is the key thing an agent needs to chain follow-up calls. Only pagination/limit behavior and the relation to cotlet_browser_close remain unstated.

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%, so both `app` and `url` are already documented in the schema, and the description adds only the routing rule (site's open tab, else new tab). It never mentions the `app` parameter's purpose in prose, leaving the schema to carry that weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Starts the user's Cloud Browser ... and opens `url`') and states scope precisely: a real signed-in Chrome, tab-reuse behavior, and the page contents returned. This distinguishes it cleanly from siblings like cotlet_browser_navigate and cotlet_browser_read.

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' gives clear sequencing guidance relative to the action siblings, and the Gladly action list signals the workflow context in which the browser is the entry point. It stops short of explicitly naming when to use cotlet_browser_navigate instead, so it falls just below the top score.

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

All Gladly MCP Server and API 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?