meta-description-generatorMeta Description Generator: Write SEO meta descriptions that maximize click-through rate. (free, AI-generated, rate-limited).
| Name | Required | Description | Default |
|---|---|---|---|
| tone | No | Optional tone, e.g. professional, playful. | |
| topic | No | ||
| keyword | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description adds 'rate-limited' which is a useful operational constraint beyond the annotation. However, it does not disclose output format, expected number of descriptions, or behavior when rate limits are hit. The added value is minimal but non-zero, so a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded, with a single sentence plus a parenthetical. However, it begins with 'Meta Description Generator:' which repeats the tool title, wasting words. Otherwise, it is tightly written with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has only 3 parameters and no output schema, but the description does not provide the necessary parameter guidance or return format. Given the low schema coverage, the description should carry more of the explanatory burden. It explains what the tool does but not how to use it or what to expect, making it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low (33% - only 'tone' has a description). The tool description does not compensate by explaining 'keyword' or 'topic' semantics. It only vaguely implies the keyword is the main input through the purpose. This is insufficient given the low coverage, hence a score of 2.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('Write'), a specific resource ('SEO meta descriptions'), and a purpose ('maximize click-through rate'). This distinguishes it from sibling tools like seo-title-generator and ad-copy-generator by focusing on meta descriptions specifically.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The purpose implies when to use it (for generating meta descriptions), but there is no explicit guidance on alternatives or exclusions. The parenthetical 'free, AI-generated, rate-limited' gives context but does not compare to siblings. It meets the 'implied usage' level, not clear contextual guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but word-counter and character-counter overlap heavily, and meta-tag-generator subsumes several other generators (title, description, canonical). The sheer number of adjacent content generators creates some ambiguity, though descriptions generally clarify.
Tool names are inconsistent: some use snake_case (create_site, get_article, list_articles) while others use hyphenated lowercase (ad-copy-generator, meta-tag-generator, robots-txt-generator). This mixing of conventions makes it hard for an agent to predict the name for a given action.
With 59 tools, the server is heavily over-scoped for a typical MCP server. Many tools are similar (various calculators, many content generators) and could be consolidated, making the surface bloated and harder to navigate.
The server covers a broad range of SEO tasks: site management, article generation/publishing, analytics, technical SEO, and content tools. However, there are gaps such as missing update/delete operations for articles and no backlink analysis, leaving some workflows incomplete.