Website Audit MCP

audit_website

Fetch one HTTP/HTTPS URL and score it 0-100 for performance, SEO, design, functionality, and technology, returning findings to identify technical strengths and weaknesses.

Instructions

Fetch one http/https URL and score it 0-100 for performance, SEO, design, functionality and technology, with findings.

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_website"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	http or https URL of the page to audit

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations exist, so the description bears the full disclosure burden, and it leaves most behavioral questions open. It never says whether the page is rendered with JavaScript, how long an audit takes, whether there are rate limits or auth requirements, or whether the fetch can fail on blocked/paywalled pages. It does disclose the return content (five category scores 0-100 plus findings), which is the main piece of added behavior.

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?

A single front-loaded sentence with the verb and scope first, then the scoring dimensions and the 'with findings' tail. Nothing is redundant. It is compact but thin, so it sits just below the top mark rather than at it.

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

Completeness4/5

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

For a one-parameter read tool with no output schema and no annotations, the description covers what is fetched, how it is scored, and that findings are returned. Missing are latency, failure modes, and any hint about the response structure. These are real gaps but modest against the tool's simplicity.

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 a single required 'url' parameter already documented as an http or https page address. The description restates that it takes one http/https URL and adds no format, length, or validation detail beyond the schema. Baseline of 3 is appropriate given the schema does the work.

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

Purpose4/5

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

The description names a concrete verb (fetch) and resource (one http/https URL) and states the output shape: a 0-100 score across performance, SEO, design, functionality and technology, plus findings. The phrase 'one URL' implicitly separates it from compare_websites, which handles multiple sites, though that sibling is never named. Only the lack of an explicit sibling contrast keeps it from a 5.

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?

Usage is only implied: an agent can infer you call this to audit a single page, and that compare_websites is the multi-site alternative. There is no explicit when-to-use, when-not-to-use, or prerequisite statement. An agent must reason from the word 'one' to pick between this and its sibling.

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

Deploy Server