Skip to main content
Glama

쿠팡 상품 조회

coupang_product
Read-only

Coupang product by URL or product id: title, prices, discount, rating, reviews, stock, seller, options, categories and images. Sold-out items are returned and billed (is_in_stock false, price may be empty). 쿠팡 상품 주소 또는 상품번호로 상품명·정가·판매가·할인율·평점·리뷰 수·재고·판매자·옵션·카테고리·이미지를 조회합니다. 품절 상품도 정상 응답이며 과금됩니다(is_in_stock false, 판매가 빈 값 가능). [호출당 30포인트]

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

Input Schema

NameRequiredDescriptionDefault
urlNo쿠팡 상품 주소 (/vp/products/ 형식, url 또는 product_id 중 하나 필수)
product_idNo쿠팡 상품번호 (숫자)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the commercial cost ('[호출당 30포인트]') a caller incurs on every invocation, and by spelling out the counterintuitive edge case that sold-out items still return successfully and are still billed, with price possibly empty. That is exactly the kind of consequence information an agent cannot infer from structured fields.

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 content is front-loaded and the important facts (returned fields, sold-out billing, per-call cost) lead. However, the entire description is duplicated verbatim in Korean, roughly doubling length without adding information for most agents; the redundancy costs tokens even if the localization intent is legitimate.

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 carries the return-shape burden and does so by enumerating returned fields and the sold-out case. It is nearly complete, missing only failure behavior for an invalid URL or for supplying neither identifier, which the schema text covers only partially.

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 already fully documented in-schema, so the description only needs to avoid contradicting it. It reinforces the identifier options ('URL or product id') without adding format details such as URL variants or whether both may be passed together, so it sits near the baseline for a fully documented two-parameter schema.

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?

Names a specific resource and verb ('Coupang product by URL or product id') and enumerates exactly what comes back: title, prices, discount, rating, reviews, stock, seller, options, categories, images. It is unambiguous what the tool fetches, though it never names the obvious alternative (amazon_product) to pin down when a different product-lookup tool is preferred.

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

Usage Guidelines3/5

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

Usage is only implied: you supply a Coupang URL or product number. The critical selection rule (one of url or product_id must be given) lives in the schema property descriptions rather than the prose, and there is no statement about when to prefer this over the sibling marketplace tools or what to do with a non-Coupang URL.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.