Mailshake MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Mailshake it covers these actions: List campaigns, Add recipients to a campaign, List replies and leads, Reply to a lead, Add a follow-up to a campaign, Move leads to another campaign, Pause a campaign or recipient, Set lead status.

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_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Mailshake.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds meaningful behavioral context the annotations do not: the call is free and consumes no browser session, and it degrades gracefully to a general method for apps outside the catalog. It does not describe response shape or size, which is a minor gap with no output schema.

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 core instruction and the 'call before the first browser step' rule early, with no filler sentences. The trailing eight-item Mailshake action list is dense but arguably earns its place by telling the agent which app actions the guide covers; it could be trimmed or pushed later for tighter reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 burden of explaining returns and does so thoroughly (browser choice, sign-in link, method, screens, notes, dedicated tools). For a two-parameter, read-only guidance tool, nothing an agent needs before calling is missing.

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

Parameters4/5

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

Schema coverage is 100% and both parameters are documented, so the baseline is 3. The description nonetheless adds semantics: the app identifier may be a Cotlet slug or a plain name, defaults toward Mailshake, and an unrecognized app still yields the general method rather than an error — behavior the schema cannot express.

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 description makes clear this is a pre-flight guide rather than an action tool, and enumerates exactly what it returns: which browser to use, the sign-in link, the step-by-step method, the app's screens/menus/actions, notes, and the app's dedicated tools. It is distinguishable from siblings like cotlet_apps and cotlet_browser_click, though the leading sentence ('How to work in an app by clicking...') is more a contents list than a crisp verb+resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a concrete ordering rule — 'Call it before the first browser step in an app' — plus scope ('works for any web app; one outside Cotlet's catalog gets the general method') and a cost condition ('Free, no browser session'). An agent knows both when to call it and what it gets for uncataloged apps.

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

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