An MCP server that provides Wix API integration with OAuth 2.0 authentication, allowing users to list sites and query products from Wix e-commerce platforms
Two tools with minimal quality. 'Query Products' has a basic schema but both tools lack parameter descriptions entirely. Descriptions are present but generic (34-45 chars, below the 50-200 char LLM-optimized baseline). No output schemas documented. No error handling guidance. No tool annotations. Naming is acceptable but descriptions do not explain WHEN to use each tool or what the LLM should expect back.
Query products for a wix site
List all sites for the current user
Tool 'list sites' has empty input schema ({}). No parameters documented means LLM cannot reason about inputs.
No parameter descriptions. 'Query Products' accepts siteId but provides no guidance on format, constraints, or how to obtain it. LLM must guess.
No output schemas documented. Both tools return JSON text wrapped in content array, but LLM does not know what fields to expect in the Wix API response. Breaks downstream tool chaining.
Descriptions are too short (34-45 chars, below 50-char minimum for LLM optimization). 'List all sites for the current user' does not explain when to call this vs other discovery tools or what structure is returned.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
No error handling guidance. If Wix API returns 401 (invalid token) or 404 (site not found), the LLM sees raw HTTP status text with no recovery path. Should return actionable errors like 'Token expired. Refresh via OAuth.' or 'Site not found. Call list_sites() to see available sites.'