korea-ecommerce-integrated-channel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| channel_capabilitiesA | Show installed connectors, configuration state, and supported operations. |
| profile_listA | List local payload profiles that can turn one master product into channel bodies. |
| profile_previewA | Render a reviewed profile without calling any external seller API. |
| channel_healthB | Report configuration and connector-supported checks; inspect network_checked. |
| product_publishA | Preview or create one master product across all selected channels in parallel. |
| product_updateA | Preview or update a mapped product across selected channels in parallel. |
| product_stopC | Preview or stop a product on every selected channel. |
| product_resumeB | Preview or resume a product on every selected channel. |
| product_deleteB | Preview or permanently delete a mapped product across selected channels. |
| product_getA | Read the canonical product and its per-channel external identifiers. |
| operation_getA | Read a persisted operation, including per-channel partial failures. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Tools are mostly distinct: product lifecycle actions (publish/update/stop/resume/delete) are clearly separated, and profile operations are separate from channel state. Some overlap exists between channel_capabilities and channel_health, but their focus (installed config vs. health checks) is distinct enough to avoid confusion.
Most tools follow a noun_verb pattern (e.g., product_get, product_publish), but channel_capabilities and channel_health use noun_noun state descriptors. Also, profile_list uses 'list' for retrieval while product_get uses 'get', introducing inconsistent verbs for similar operations.
11 tools is well within the ideal 3-15 range for an e-commerce channel management server. Each tool covers a distinct aspect of the workflow (channel inspection, profile management, product operations, and async tracking), so none feel redundant or excessive.
The product lifecycle is well covered with publish, update, stop, resume, and delete, plus retrieval. Profile management is limited to list and preview (no CRUD), and there is no product listing/search, but core publishing, syncing, and operation tracking are present. Minor gaps remain around profile editing and broader product enumeration.