social-post-generatorSocial Media Post Generator: Write platform-specific social media posts. (free, AI-generated, rate-limited).
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | ||
| platform | No | Optional network, e.g. LinkedIn, X. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond the readOnlyHint annotation, noting that the tool is free, AI-generated, and rate-limited. This is useful operational information. However, it does not detail the output format or any limitations beyond rate limits, but given the annotation covers safety, the extra context merits a 4.
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 a single, efficient sentence plus a parenthetical. It front-loads the purpose and adds concise operational context (free, AI-generated, rate-limited). No unnecessary words or redundancy.
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?
For a simple tool with two parameters and no output schema, the description is minimally adequate. It lacks information on what the generated posts look like, whether multiple options are returned, or any usage examples. The rate-limit and platform-specific notes are helpful, but the description does not fully explain the return value or expected output, leaving a gap in completeness.
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 50%, with only 'platform' having a description. The text 'platform-specific' hints at the platform parameter but does not clarify the 'topic' parameter or provide details on how platform values affect output. The description adds minimal value over the schema.
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 clearly states the tool writes platform-specific social media posts, with a specific verb ('Write') and resource ('social media posts'). It distinguishes itself from sibling tools like ad-copy-generator and content-idea-generator by focusing on social media posts and platform specificity.
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 description does not provide explicit guidance on when to use this tool versus alternatives. It mentions 'platform-specific' but does not state when to choose this over other content generators, nor does it offer any exclusions or alternative tool references.
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.