MCP server for email marketing platform with audience, campaigns, broadcasts, sequences, forms, posts, sales, Stripe integration, and deliverability management
Critical failures across all dimensions. The 12 tools are registered as factory functions (registerAudience, registerTags, etc.) but their actual tool definitions are not visible in the provided source. Only the registration functions are shown; the actual tool schemas, input parameters, and output structures cannot be verified. Per HARD SCORING RULE: 'If you cannot see the actual tool definition in the source (only inferred): cap that tool's overall at 50.' Since NO tool definitions are visible, only registration stubs, all tools score at or near the cap. Additionally, the registration functions themselves have trivial descriptions ('Register audience management tools') that are under 20 characters of meaningful content, violating the description baseline. No input schemas, parameter descriptions, or output documentation are visible. This is a structural problem: the server exposes 12 tools but provides no evidence of their actual definitions.
Register audience management tools
Register broadcast management tools
Register campaign management tools
Register deliverability management tools
Register form management tools
Register operations management tools
Register post management tools
Register sales management tools
Tool definitions not visible in source. Only registration function stubs shown (e.g., registerAudience, registerTags). Actual tool schemas, input parameters, descriptions, and output structures cannot be verified.
Tool descriptions are trivial factory labels ('Register audience management tools', 'Register tag management tools', etc.), all under 20 characters of meaningful content. No descriptions explain WHAT each tool does, WHEN to use it, or WHAT it returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
Register segment management tools
Register sequence management tools
Register Stripe integration tools
Register tag management tools
No input schemas visible for any tool. Cannot verify parameter types, constraints, enums, or descriptions. LLMs cannot determine valid inputs.
Tool naming uses 'register*' prefix (registerAudience, registerTags) instead of action verbs (create_, update_, delete_, list_, search_). 'Register' is a meta-operation (tool registration) not a domain action. LLMs cannot infer what calling registerAudience actually does to the system.
No error handling, recovery guidance, or output documentation visible. Cannot verify if tools return structured objects, handle failures gracefully, or guide LLM recovery. No evidence of idempotency, pagination, or result limits.