Skip to main content
Glama
Sign In
Coupang MCP Server

Coupang MCP Server

by space-cap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_deeplinks

Converts regular Coupang URLs into shortened tracking links with affiliate code for monetization and analytics.

Instructions

Convert Coupang product URLs to affiliate tracking deeplinks. Takes regular Coupang URLs and converts them to shortened tracking URLs with your affiliate code. Useful for creating trackable links from search results or specific product pages.

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": {
      "coupang_urls": "<coupang_urls>"
    },
    "name": "create_deeplinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
coupang_urlsYesList of Coupang product URLs to convert (e.g., ['https://www.coupang.com/vp/products/184614775'])
sub_idNoOptional tracking/sub ID for analytics (uses environment default if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so description carries burden. It explains conversion to shortened tracking URLs with affiliate code, but omits details like rate limits, error handling, or whether URLs must be valid Coupang links.

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, front-loaded with action, no redundancy. Every sentence adds 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?

Covers purpose and parameter usage sufficiently for a simple tool with no output schema. Could mention output format but overall adequate.

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 100%, so baseline 3. Description adds that sub_id uses environment default if not provided, slight extra value beyond schema fields.

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?

Clearly states it converts Coupang URLs to affiliate tracking deeplinks. Specific verb+resource, and distinguishes from sibling tools which search or get products.

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?

Explicitly says it's useful for creating trackable links from search results or specific product pages, giving clear context. No exclusions stated, but enough guidance for typical use.

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