SEOctopus

Overview Schema Source Related Servers Discussions Admin

audit_site

Crawl and audit a website by providing a starting URL. Set crawl depth and page limits to uncover technical SEO issues and site structure.

Instructions

Crawl and audit an entire website

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "audit_site"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Starting URL
`maxPages`	No	Maximum pages to crawl
`maxDepth`	No	Maximum crawl depth

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are absent, so description must compensate. It states 'crawl and audit' but does not disclose behavioral details such as whether it modifies data, rate limits, or what specific audits are performed. This leaves uncertainty for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single short sentence, no wasted words. However, it could be slightly more informative without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists. The description does not explain what the audit produces (e.g., report, issues list, scores). Given the complexity of crawling an entire site, the description is too sparse to fully inform an agent about what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with all three parameters described in the schema. The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it crawls and audits an entire website, using a specific verb and resource. It is well-distinguished from sibling tools like audit_page (single page) and audit_links (specific audit type).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives are mentioned. The purpose is implied by the tool name and siblings, but no guidance on choosing between full site audit vs. page-level or specific audits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.