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_batch_update_price_stock

Update product prices and stock in bulk across Shopee, TikTok, Lazada, and LnwShop while avoiding rate limits and pausing for captcha resolution.

Instructions

อัปเดตราคาและสต็อกแบบหลายรายการพร้อมระบบชะลอความเร็วเพื่อป้องกันการโดน Rate-Limit

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>",
      "items": "<items>"
    },
    "name": "ecommerce_batch_update_price_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It does disclose a meaningful behavior—throttling to prevent rate limits—but does not mention failure handling, partial success, authentication, or side effects beyond updating.

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?

The description is a single, front-loaded sentence with no filler. It conveys the core action and a key behavioral safeguard in minimal space.

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?

The tool has no annotations, no output schema, and moderate schema complexity with nested items and a platform enum. The description leaves out important context such as required identifiers, optional fields, platform constraints, and expected result or error behavior.

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%, so the description needed to compensate for parameter meaning. It mentions price and stock, which loosely maps to newPrice and newStock, but adds no detail about productId, skuId, or the platform enum.

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 clearly states a specific action: updating price and stock in batch. The phrase 'แบบหลายรายการ' (multiple items) distinguishes it from the singular sibling ecommerce_update_price_stock, though it does not name that sibling explicitly.

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?

The description implies usage for batch price/stock updates and mentions throttling to avoid rate limits, which suggests when it is preferable over individual updates. However, it does not explicitly state when not to use it or name alternative tools.

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