Generates a comprehensive digital marketing strategy blueprint, buyer intent & funnel mapping, CRO recommendations, AEO AI overview tactics, and a 30-60-90 day growth roadmap.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | Target file path or live URL. | |
| projectPath | No | Optional project root directory. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description is the only behavioral signal. It does disclose what the tool produces and names five output components, but it does not disclose side effects, whether files are written to projectPath, authentication needs, or return format. This is a meaningful but incomplete behavioral picture.
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?
One dense sentence with no filler, and the most important deliverable ('digital marketing strategy blueprint') is front-loaded. It could be slightly better structured with separators, but it is efficient.
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 2-parameter tool with no output schema and no annotations, the description gives a good list of deliverable categories but omits how the target is used, whether projectPath receives output files, and what the returned artifact looks like. It is adequate but leaves clear gaps.
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%: target is described as 'Target file path or live URL' and projectPath as 'Optional project root directory.' The description adds no parameter detail beyond what the schema already provides, so the baseline of 3 is appropriate.
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 opens with a specific verb ('Generates') and names a concrete deliverable: a digital marketing strategy blueprint, plus buyer intent/funnel mapping, CRO recommendations, AEO tactics, and a 30-60-90 day roadmap. This clearly distinguishes it from sibling audit and code-fix tools.
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 implies a use case—when a marketing strategy, funnel mapping, and growth roadmap are needed—and the sibling tools are mostly audits, so context is inferable. However, it provides no explicit when-to-use, when-not-to-use, or alternative tool names, leaving the agent to infer selection criteria.
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.