Constant Contact 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 Constant Contact it serves these actions: Get email report, List contacts who did not open, Create list, Add contacts to list, Copy email, Schedule email.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint=false, so the description is free to add the traits that matter: it runs in the user's signed-in Chrome, reuses the site's existing tab instead of spawning one, and leaves the user's own tabs untouched. It also discloses the return shape (in-view elements and text) despite no output schema; it omits what a repeat call does, which matters given idempotentHint=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 imperative and the sequencing cue are front-loaded, then behavior, then return value, in a tightly ordered sequence with no filler. The final sentence enumerating five Constant Contact actions is tangential to a generic browser-open tool and reads as app-specific boilerplate that dilutes an otherwise lean definition.

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 usefully states what comes back after the page answers, which an agent needs to chain the next step. For a two-parameter, fully documented, annotated tool this is close to complete; only repeat-call behavior and cost implications are unaddressed.

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% with both parameters documented inline, including the `app` escape hatch, so the schema carries the semantics. The description adds only the destination behavior for `url` (existing site tab, else a new tab) and says nothing about `app` beyond the schema text, 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?

"Starts the user's Cloud Browser ... and opens `url`" gives a concrete verb and resource, and the detail that it is a real Chrome where the user is signed in distinguishes it from a generic navigation call. It never names cotlet_browser_navigate, so the boundary with that sibling must be inferred, and the closing Constant Contact sentence muddies rather than sharpens the purpose.

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 explicit sequencing guidance an agent can act on, and the tab-reuse rule explains the practical consequence of choosing this tool. There is no when-not guidance and no named alternative for navigating an already-open browser, which is the main gap.

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

All Constant Contact 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?