Skip to main content
Glama
Sign In
Openworker E-Commerce MCP Server

Openworker E-Commerce MCP Server

by tukimtk-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ecommerce_manage_promotions

Create, list, and update Flash Sales and voucher campaigns across Shopee, TikTok Shop, and Lazada using browser automation.

Instructions

Query and update store Flash Sales and voucher campaigns

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": {
      "platform": "<platform>",
      "action": "<action>"
    },
    "name": "ecommerce_manage_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
platformYes
promoDetailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. While 'update' conveys mutation, it does not warn about potential side effects of create/update on live store campaigns, nor does it mention permissions, rate limits, or payload requirements.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler, making it easy to parse. It loses a point because the missing 'create' action makes the concise phrasing slightly misleading rather than merely compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, a nested object, no annotations, and no output schema, the tool needs far more context than one sentence provides. The description lacks platform constraints, promoDetails structure, action-specific behavior, and expected return information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the semantics of 'platform', 'action', or 'promoDetails'. It only frames the domain, so it fails to compensate for the schema's lack of parameter documentation.

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 concrete action ('Query and update') and a specific resource ('store Flash Sales and voucher campaigns'), making the tool's general purpose clear and differentiating it from product/order-focused siblings. However, it omits 'create', which appears in the action enum, so the stated scope is slightly incomplete.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions. It relies entirely on the reader to infer that this is for promotions management, with no explicit context or routing signal.

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