Skip to main content
Glama
Sign In

ClickSend MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 ClickSend it serves these actions: Create SMS campaign, Send SMS, Cancel scheduled SMS, List SMS history, Add contacts, Remove opted-out contacts, Remove duplicate contacts, Add to Opt-Out List.

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

NameRequiredDescriptionDefault
appNoLeave 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.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent=false/destructive=false, and the description adds real behavior on top: the target is a real Chrome where the user is signed in, the URL lands in the site's existing tab or a new one, user tabs are preserved, and the call answers with the in-view elements and text using the same numbering. It never states session lifetime or what happens if the browser can't launch, which keeps it off 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.

Conciseness4/5

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

Front-loaded with the action and the ordering rule, then behavior, then use cases — a sensible ordering. Minor waste: "with the same numbers" and "Answers the page after it" are terse to the point of being cryptic, and the ClickSend action enumeration is long relative to the rest.

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 carries the return-value burden and does so ("the elements and text in view"), and it establishes that a signed-in browser session is the execution context. Only the multi-step handoff (what to call after the page is open) is left implicit, which is acceptable for this simple 2-param entry point.

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 both parameters are already described in the schema, including the app-slug pattern and the omission default. The description adds only the imperative "call it first" framing, not new meaning for `url` or `app`, so the baseline 3 applies.

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?

Names a specific verb and resource ("Starts the user's Cloud Browser ... and opens `url`") and scopes it to the user's real signed-in Chrome, which separates it from the rest of the browser_* family (read, navigate, click). The trailing ClickSend action list makes the downstream use concrete rather than abstract.

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 explicit ordering guidance within the browser workflow, and the app-parameter note tells the agent when to leave the parameter out. It stops short of naming a follow-up/alternative (e.g. use cotlet_browser_navigate to move to another URL later), so no explicit when-not-to-use condition is stated.

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

All ClickSend MCP Server and API by Cotlet toolsInspect
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