Skip to main content
Glama
Sign In

WooCommerce 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 WooCommerce it serves these actions: List orders, Update order status, Create refund, Create coupon, Update product, Get sales report.

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
Behavior5/5

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

Goes well beyond the annotations by disclosing that this is the user's real signed-in Chrome (auth context the agent must assume), that the page loads into the site's existing tab so the user's own tabs survive, and what comes back afterwards (visible elements and text with stable element numbers). It also lists the WooCommerce actions this entry point enables, which no annotation conveys.

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?

Tight and front-loaded: purpose first, then ordering instruction, then tab behavior, then return shape. A few phrasings are cryptic ('with the same numbers'), and the trailing WooCommerce action list is tangential to opening a browser, but nothing is padded fluff.

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 summarizes the post-open payload (elements and text in view) and the numbering scheme used by later click/type steps. The auth and signed-in-state context is the key missing piece an agent would otherwise have to infer, and it is present.

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 the `app` parameter is already fully explained in the schema, including its e.g. milanote pattern. The description adds one useful behavioral detail about `url` routing (existing site tab, else new tab), but otherwise the schema carries the parameter burden.

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 specific verb and resource: 'Starts the user's Cloud Browser ... and opens `url`', and defines the browser as a real signed-in Chrome, which is concrete. It does not explicitly contrast itself with the sibling cotlet_browser_navigate, though 'Call it first' implies it is the session entry point rather than a follow-up navigation.

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 a clear ordering rule for the browser tool family, and the schema's `app` description tells the agent when to omit it. There is no explicit when-not condition (e.g. what to do if a browser session is already open), which keeps it below a 5.

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

All WooCommerce 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