WooCommerce 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 WooCommerce it covers 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_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: WooCommerce.
`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

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral facts: it is free, opens no browser session, and degrades gracefully to a general method for uncatalogued apps. What it does not disclose is the response shape (sections vs prose) or how large the returned guide is, which matters for a context-consuming guidance tool.

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 purpose and call-timing are front-loaded, which is good, but the opening sentence is a long comma-chained inventory of contents ('the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools') that could be trimmed. The trailing WooCommerce action list is useful scoping evidence but adds bulk disproportionate 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?

For a two-optional-parameter guidance tool with no output schema, the description tells the agent what it will get back (browser/sign-in, step method, screens, notes, dedicated tools) and when it is cheap to call. Only the format and size of the returned guide remain unspecified.

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%, so both optional parameters are already documented in the schema (app name/slug with default WooCommerce, task in user's words). The description adds only indirect hints — the catalogue-scoped vs general method tied to the app, and the WooCommerce action list showing expected task granularity — but never explains how `task` shapes the returned guidance. 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?

The description states a specific resource: a how-to guide for operating a web app through Cotlet's browser tools, enumerating what it returns (browser choice, sign-in link, method, screens, menus, actions, notes, dedicated tools). It is clearly distinguishable from the cotlet_browser_* action tools and from woocommerce_* tools, though the exact verb ('returns guidance') is implied rather than stated.

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 before the first browser step in an app' gives an explicit trigger point, and 'Works for any web app; one outside Cotlet's catalog gets the general method' sets scope expectations. The mention of 'the app's dedicated tools when Cotlet has them' hints at preferring native tools but never states an explicit preference rule or exclusion, so it stops short of full when-vs-alternative guidance.

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