Trengo 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 Trengo it serves these actions: List conversations, Search conversations, Read a conversation, Add label, Assign conversation, Reply to customer, Add internal note, Close conversation, Set reminder.

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/5.0

Behavior5/5

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

Adds real context beyond the annotations: the browser is a real Chrome where the user is already signed in (auth state), the URL is routed to the site's existing tab so the user's tabs are preserved (side-effect profile beyond destructiveHint=false), and it discloses what comes back since no output schema exists. The Trengo action list also signals scope of use.

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?

The core is front-loaded and efficient, but the trailing sentence enumerating Trengo actions (List conversations, Search conversations, ...) largely restates sibling tool names and dilutes focus. The phrase 'with the same numbers' is also unexplained shorthand.

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 session-starting tool with no output schema, the description covers auth context, tab behavior, session ordering, and a sketch of the returned page content. The only gap is that the referenced element 'numbers' are not explained as cross-tool identifiers.

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 description coverage is 100% and the `app` parameter's leave-it-out guidance is fully documented in the schema itself. The description's tab-routing sentence adds behavioral meaning to `url` but no syntax, format, or validation detail beyond the schema, so baseline 3 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?

States a concrete verb+resource: starts the user's Cloud Browser and opens `url`, with the 'Call it first' ordering cue. It is weakened slightly by not naming its closest sibling, cotlet_browser_navigate, so an agent must infer the difference from the 'opens url / call first' phrasing.

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 rule, and the tab-routing sentence tells the agent this is the entry point for a browsing session. It stops short of naming when NOT to use it or pointing to alternatives like cotlet_browser_navigate or cotlet_browser_tabs.

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

All Trengo 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?