MarketMan MCP Server and API by Cotlet

Create purchase order in MarketMan

marketman_create_purchase_order

Read-onlyIdempotent

Create purchase order in the user's own MarketMan account from ChatGPT, Claude or any AI agent. Returns how to do it in MarketMan step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's MarketMan Cloud Browser. MarketMan's official API: MarketMan has a REST API (V3), but it needs an API Partner key and password, and its pricing page lists Open API Access as read-only in Enterprise or a paid add-on on Starter and Growth (checked 28 Oct 2026).

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": "marketman_create_purchase_order"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description confirms this behaviorally ('opens nothing by itself'), so there is no contradiction despite the 'create' name. It adds real context beyond the annotations: the output is a navigation guide and the actual mutation happens through browser tools, plus the API-access restriction. It omits whether a Cloud Browser session must already be open, which would matter for sequencing.

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 core behavior is front-loaded and easy to extract, but the final sentence about the REST API, partner keys, pricing tiers, and a 'checked 28 Oct 2026' date is long and reads as justification rather than instruction; the 'from ChatGPT, Claude or any AI agent' clause is filler. Trimming those would sharpen the definition without losing routing value.

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 parameters and no output schema, the description carries the burden of describing the return value, and it does so at a high level (step-by-step screens, buttons, fields). What is missing is the precondition — whether the MarketMan Cloud Browser must be opened first — which an agent needs to sequence the subsequent browser calls correctly.

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?

The tool takes zero parameters, so the baseline is 4. The description introduces no parameter-like inputs, consistent with the empty schema, and does not confuse the agent into expecting arguments.

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 names a specific verb and resource (create purchase order) and then clarifies the actual mechanism: it returns step-by-step instructions (screens, buttons, fields) rather than performing the action. That clarification is essential because the name/annotations pair looks contradictory otherwise. The opening framing ('from ChatGPT, Claude or any AI agent') adds marketing noise rather than distinguishing scope.

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?

It explicitly routes the agent: call this, then execute with cotlet_browser_* tools in the user's MarketMan Cloud Browser. It also pre-empts the obvious alternative (MarketMan's official V3 REST API) by explaining the partner-key/pricing/read-only constraints that make it unusable. No explicit statement of when *not* to call this, but the workflow chain is clear.

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

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