Skip to main content
Glama
Sign In
coupang-browser-mcp

coupang-browser-mcp

by hanjoonchoe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove from cart

remove_from_cart
Destructive

Remove an item from the cart by product name. Use confirm=false to narrow to one match, then confirm=true to perform removal.

Instructions

Remove an item from the cart. With confirm=false (default) it only returns items matching the name — narrow to exactly one match, then call again with confirm=true to remove.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productName": "<productName>"
    },
    "name": "remove_from_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
productNameYesProduct name to remove (partial match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, but the description adds valuable context: the confirm parameter controls preview vs actual removal, and the tool returns matching items when confirm=false. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no redundant information. Critical behavior is front-loaded. Every sentence serves a purpose.

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?

Given the tool has only two parameters and no output schema, the description sufficiently covers the essential workflow. It could mention the return format of the preview step, but overall completeness is high.

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 describes productName with partial match, but lacks description for confirm. The description compensates by explaining confirm's role (preview vs removal). This adds essential meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action ('Remove an item from the cart') and distinguishes itself from siblings like add_to_cart (adds) and get_cart (reads). The two-step process with confirm parameter is clearly explained.

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?

The description provides clear usage guidance: use confirm=false to preview matching items, then narrow to one match and call again with confirm=true to remove. It does not explicitly state when not to use, but the two-step pattern is well-defined.

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

Deploy Server

Other Tools