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_sync_product_images

Extract product gallery images from one platform, re-format them, and upload to multiple e-commerce stores in a single operation.

Instructions

Extract, re-format, and upload product gallery images across platforms

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": {
      "sourcePlatform": "<sourcePlatform>",
      "targetPlatforms": "<targetPlatforms>",
      "productId": "<productId>"
    },
    "name": "ecommerce_sync_product_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYes
sourcePlatformYes
targetPlatformsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 carry the burden of behavioral disclosure. It only states the high-level operation and does not say whether existing target gallery images are overwritten, appended, or left untouched, nor does it mention permissions, idempotency, or failure behavior.

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 tight sentence with no filler and front-loads the main action. It is concise, though slightly too sparse to fully carry the required behavioral and parameter context.

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?

For a mutating multi-platform operation with no annotations, no output schema, and 0% schema description coverage, this one-line description is incomplete. An agent cannot confidently know what will happen to target galleries, what platform identifiers are valid, or what the tool returns after execution.

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 adds no parameter-specific information. It never explains accepted values for sourcePlatform or targetPlatforms, how productId identifies the gallery, or any format constraints. 'Across platforms' is the only indirect hint and is insufficient.

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?

The description names a specific capability: extracting, re-formatting, and uploading product gallery images across platforms. This clearly distinguishes it from stock-sync, clone-product, or other sibling tools.

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?

There is no mention of when this tool should be used instead of alternatives such as ecommerce_sync_multiplatform_stock or ecommerce_clone_product. The intended use case is only implied by the phrase 'across platforms' and the tool name.

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