Discovers related website ecosystems, infers market vertical & competitor archetypes, suggests high-authority directory/backlink targets, and generates keyword topic clusters.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | Directory path to the website codebase or a live URL (https://...) to analyze. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description carries the full burden of behavioral disclosure, but it only lists outputs and does not state whether the tool is read-only, whether it mutates anything, what input restrictions apply, or how results are returned. The verbs 'discovers' and 'suggests' imply a non-destructive analysis, but this is not explicit.
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, front-loaded sentence with no filler or repetition. Each clause names a distinct and relevant output, making the description information-dense and easy for an agent to parse quickly.
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 tool with one parameter and no annotations or output schema, the description adequately names the main functions but leaves important context unstated, such as the format or structure of the returned suggestions, whether results are persisted, and any constraints on the input. This is a meaningful gap for an agent deciding whether and how to invoke the tool.
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 coverage is 100% and the single parameter 'target' is already well described as a directory path or live URL. The tool description adds no further meaning about how the target should be formatted, what kinds of URLs are accepted, or how the parameter relates to the generated output, so the description adds no value beyond the schema here.
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 names a specific multi-step activity with concrete resources: discovering related website ecosystems, inferring market verticals and competitor archetypes, suggesting backlink targets, and generating keyword topic clusters. This clearly differentiates the tool from sibling audit and generation tools, which focus on site audits, fixes, or marketing strategy rather than ecosystem/backlink discovery.
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 explains what the tool does but not when to use it versus other SEO tools. There is no mention of scenarios, prerequisites, or why this tool would be chosen over seo_audit_* or seo_generate_marketing_strategy. The usage context is only weakly implied by the output types.
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 audit tools target distinct SEO dimensions, but several overlap: seo_audit_technical, seo_audit_robots_and_sitemap, and seo_audit_sitemap_multipage all involve robots.txt, sitemaps, and header checks. The descriptions help, but an agent could easily misselect between these related tools.
All tools follow a consistent seo_ prefix with clear verb_noun snake_case naming: audit_, crawl_, discover_, generate_, suggest_, test_, validate_. There is no mixing of conventions or vague generic verbs.
With 21 tools, the server sits in the 16-25 'heavy' range. The broad SEO scope justifies many of them, but the large number of overlapping audit variants makes the set feel slightly bloated.
The server covers the SEO lifecycle well: discovery, crawling, dimension-specific audits, full audits, code fixes, sitemap/robots generation, and validation. Minor gaps such as dedicated backlink or mobile usability audits exist, and the '8-dimension' full audit claim does not align with the 12 distinct audit tools.