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_autonomous_store_manager

Start or stop a background agent that autonomously manages e-commerce store operations, including product updates across Shopee, TikTok Shop, and Lazada, while handling captcha pauses.

Instructions

Background agent loop for autonomous store management

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

Input Schema

NameRequiredDescriptionDefault
actionYes
intervalMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden, but it only says 'background agent loop.' It does not disclose side effects, process lifecycle, persistence, scheduling behavior, permissions, or consequences of the four actions.

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

Conciseness2/5

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

The description is short, but this is under-specification rather than effective conciseness. It provides only a vague phrase and omits essential behavioral and usage details.

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

Completeness1/5

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

This is a stateful control-loop tool with no annotations and no output schema, and the description explains none of the action semantics, intervalMs behavior, return values, or how it fits into the broader ecommerce toolset. It is far from complete for an agent to invoke correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the description never mentions action or intervalMs. All parameter meaning comes from the schema's enum and property names; the description adds no semantic value whatsoever.

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

Purpose3/5

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

The description conveys that this tool runs a background loop for autonomous store management, which is more than a tautology but still vague. It lacks a specific verb or action statement and does not differentiate itself from siblings like ecommerce_run_recipe or ecommerce_safety_guard.

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?

No guidance is given for when to use this tool versus alternatives, nor when to use start vs stop vs status vs trigger_now. The enum values in the schema imply usage, but the description itself provides no context or selection criteria.

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