This server has critical definition failures. The single tool 'execute_skill_action' lacks a visible input schema in the source code, only a description string is present. No parameter definitions, types, or constraints are documented. The description is generic (28 chars) and does not explain what the tool actually does, when to use it, or what it returns. The mcp_server.py file does not implement the MCP protocol correctly, it merely prints a JSON status message and exits, rather than establishing a bidirectional message loop. Tool registration is inferred from a string in the startup output, not from explicit schema definitions.

• Define an explicit input schema with typed parameters. At minimum: product_sku_list (array of strings), target_marketplaces (array of strings, optional, with enum constraint for known marketplaces). Add descriptions for each parameter explaining format and constraints.
• Expand the tool description to 100 - 200 characters. Example: 'Synchronize product listings across multiple social commerce marketplaces (TikTok Shop, Shopee, Lazada). Accepts a list of product SKUs and target marketplace names. Returns count of synchronized listings and sync latency.'
• Rename the tool to a more specific verb_noun pattern. Consider 'sync_product_catalog', 'synchronize_marketplace_listings', or 'push_products_to_marketplaces', something that clearly conveys the action.
• Document the output schema with field types and descriptions. Example: { synced_marketplaces: [string], synchronized_listings_count: number, sync_latency_ms: number, status: 'success'|'partial'|'failed' }.
• Add error handling with recovery guidance. Example: 'If sync_latency_ms exceeds 5000, retry with a smaller product_sku_list. If a marketplace is not found, check target_marketplaces against the supported list: [TikTok Shop US, Shopee TH, Lazada MY, ...]'.