Loading ToolBench
Auto-generates Google-compliant SEO Title and Meta Description tags using product context.
This MCP server has critical definition quality gaps. The single tool 'generate' lacks proper MCP integration patterns, has minimal parameter descriptions, no output schema documentation, and the implementation is a basic Python class without MCP server scaffolding. The tool name 'generate' is vague and generic; it should be 'generate_seo_meta' or similar. Parameter descriptions are minimal (10-15 chars each), falling well below the 72-char baseline. No error handling, validation, or recovery guidance. The server appears to be a client SDK wrapper, not an actual MCP server implementation, there is no evidence of MCP protocol transport, request/response handling, or tool registration via the MCP specification.
Auto-generates Google-compliant SEO Title and Meta Description tags using product context.
Tool name 'generate' is too generic and violates verb_noun convention. Should be 'generate_seo_meta' or 'generate_seo_metadata' to clearly signal SEO metadata generation vs. other generation tasks.
Parameter descriptions are critically short (7-20 chars). 'The product category' (22 chars) and 'List of keywords relevant to the product' (38 chars) are below the 72-char baseline. Required descriptions must explain format, constraints, and context. E.g. 'Product category (e.g., skincare, electronics). Used to generate contextually relevant SEO title and meta description.'
No output schema documented. The response returns seo_title, meta_description, title_length, description_length, but LLMs have no formal schema to understand field types and structure. Must document: { seo_title: string, meta_description: string, title_length: integer, description_length: integer }
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If keywords is empty, if brand_name contains invalid characters, or if product_name is missing, the tool will silently produce low-quality output. No validation, no error messages, no guidance for LLM recovery.
Transport is unknown. Source code contains only a Python class (client.py) with no MCP server implementation, no HTTP/SSE handlers, no STDIO transport. This is not a functional MCP server, it's a client library stub. Cannot be deployed or tested against the MCP protocol.
Brand_name parameter is optional but no default value is documented. The description says '(optional)' but does not explain what happens if omitted, the response differs based on this flag. Undocumented behavior invited LLM confusion.
No input constraints documented. Keywords array has no stated minimum/maximum length; product_name has no length limit stated (though code truncates at 60 chars). Constraints must appear in descriptions to guide LLM input.