Skip to main content
Glama

NexusBro website and SEO audit

Website and SEO audit (free)

audit_website
Read-only

Audits a public website: crawls up to 5 pages and returns a health score from 0 to 100, the top issues (SEO, page speed, broken links, accessibility, security headers), a fix prompt the user can copy into their coding agent, and a link to the full report. Use it when the user asks to audit, check or improve a website or a landing page. Takes 20 to 90 seconds. Documentation: https://nexusbro.com/api-docs#mcp

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

NameRequiredDescriptionDefault
urlYesThe public website to audit, for example example.com or https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses the crawl depth limit (5 pages), the expected latency window (20-90 seconds), and the shape of the result (score 0-100, issue categories, copyable fix prompt, report link). The latency estimate in particular is operationally useful for an agent deciding whether to call it synchronously.

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?

Purpose and scope are front-loaded, followed by the trigger condition and runtime, in roughly four sentences with no filler. The trailing documentation URL is the only element that could be considered overhead, though it is short and clearly separated.

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?

With no output schema, the description correctly compensates by enumerating what comes back, and the runtime plus page cap set reasonable expectations for a crawl-based tool. Gaps remain around failure behavior (unreachable or non-public sites) and cost/rate limits, which matter for an external-network operation.

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% and there is only one parameter, so the schema already carries the burden, including the example formats and length bounds. The description only implicitly reinforces that a specific page URL (e.g. a landing page) is acceptable; it adds no format or validation detail beyond the schema. Baseline 3 applies.

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?

Opens with a specific verb and resource ("Audits a public website") and quantifies scope ("crawls up to 5 pages") plus outputs (health score, top issues, fix prompt, report link), so the operation is unmistakable. It does not, however, distinguish itself from the sibling tool audit_checks, which an agent would have to disambiguate on its own.

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

Usage Guidelines4/5

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

Explicitly states the trigger condition: "Use it when the user asks to audit, check or improve a website or a landing page." This is a clear usage context, but it offers no when-not-to-use or any pointer to audit_checks as the alternative for related requests.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources