Skip to main content
Glama

Audit public webpage

audit_public_webpage
Read-onlyIdempotent

Use this when the user provides one live public webpage URL. Fetches one bounded static HTML response, then runs HTML validation, SEO/accessibility-signal, and JSON-LD syntax checks. It checks links only when requested and does not crawl, execute JavaScript, authenticate, or fetch linked stylesheets. Use only URLs the user owns or is authorized to inspect.

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

Input Schema

NameRequiredDescriptionDefault
urlYesOne authorized public HTTP(S) webpage URL; private pages, credentials, and custom ports are rejected.
max_linksNoMaximum links to check, from 1 to 20.
check_linksNoWhether to contact eligible public links found on the fetched page.

Output Schema

NameRequiredDescriptionDefault
errorNo
linksYes
overviewYes
html_infoYes
redirectsYes
css_errorsYes
seo_issuesYes
css_checkedYes
fetched_urlNo
html_errorsYes
http_statusNo
broken_linksYes
content_typeNo
css_messagesYes
page_fetchedYes
seo_findingsYes
failed_checksYes
healthy_linksYes
html_messagesYes
html_warningsYes
links_checkedYes
requested_urlNo
schema_issuesYes
seo_truncatedYes
eligible_linksYes
html_truncatedYes
links_requestedYes
links_truncatedYes
schema_findingsYes
schema_truncatedYes
unverified_linksYes
unreachable_linksYes
redirects_followedNo
html_total_messagesYes
schema_blocks_checkedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / content_type / const
      Removed value: -"text/html"
    • addedOutput schema / properties / content_type / enum
      Added value: +[
      +  "text/html",
      +  "application/xhtml+xml"
      +]
    • addedOutput schema / properties / eligible_links
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / links_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / schema_findings / items / properties / code
      Added value: +{
      +  "description": "Stable machine-readable audit rule identifier.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / schema_findings / items / required
      Previous value: -[
      -  "severity",
      -  "category",
      -  "message"
      -]New value: +[
      +  "code",
      +  "severity",
      +  "category",
      +  "message"
      +]
    • addedOutput schema / properties / seo_findings / items / properties / code
      Added value: +{
      +  "description": "Stable machine-readable audit rule identifier.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / seo_findings / items / required
      Previous value: -[
      -  "severity",
      -  "category",
      -  "message"
      -]New value: +[
      +  "code",
      +  "severity",
      +  "category",
      +  "message"
      +]
    • addedOutput schema / properties / unverified_links
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "html_errors",
      -  "css_errors",
      -  "seo_issues",
      -  "schema_issues",
      -  "links_checked",
      -  "broken_links",
      -  "html_warnings",
      -  "html_info",
      -  "html_messages",
      -  "css_messages",
      -  "seo_findings",
      -  "schema_findings",
      -  "links",
      -  "seo_truncated",
      -  "schema_truncated",
      -  "html_total_messages",
      -  "html_truncated",
      -  "schema_blocks_checked",
      -  "healthy_links",
      -  "redirects",
      -  "unreachable_links",
      -  "links_requested",
      -  "css_checked",
      -  "failed_checks",
      -  "overview",
      -  "page_fetched"
      -]New value: +[
      +  "html_errors",
      +  "css_errors",
      +  "seo_issues",
      +  "schema_issues",
      +  "links_checked",
      +  "eligible_links",
      +  "links_truncated",
      +  "broken_links",
      +  "unverified_links",
      +  "html_warnings",
      +  "html_info",
      +  "html_messages",
      +  "css_messages",
      +  "seo_findings",
      +  "schema_findings",
      +  "links",
      +  "seo_truncated",
      +  "schema_truncated",
      +  "html_total_messages",
      +  "html_truncated",
      +  "schema_blocks_checked",
      +  "healthy_links",
      +  "redirects",
      +  "unreachable_links",
      +  "links_requested",
      +  "css_checked",
      +  "failed_checks",
      +  "overview",
      +  "page_fetched"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / overview / properties / kind / enum
      Previous value: -[
      -  "html",
      -  "css",
      -  "seo",
      -  "schema",
      -  "links",
      -  "report"
      -]New value: +[
      +  "html",
      +  "css",
      +  "seo",
      +  "schema",
      +  "links",
      +  "report",
      +  "site"
      +]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral boundaries: it fetches only one bounded static HTML response, does not execute JavaScript, does not authenticate, does not fetch linked stylesheets, and only checks links when requested. It also adds an authorization constraint that an agent would not infer from readOnly/openWorld/idempotent annotations alone.

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

Conciseness5/5

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

The description is front-loaded with the usage condition, then states capabilities, boundaries, and the authorization requirement. It is compact, with no repetitive or wasted wording.

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

Completeness5/5

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

For a multi-check read-only audit tool, the description covers scope, capabilities, excluded behaviors, optional link checking, and authorization. An output schema exists, so return-value details need not be repeated, and the annotations are supplemented rather than contradicted.

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 description coverage is 100%, so the schema already explains url, check_links, and max_links in detail. The description reinforces that the URL must be a single authorized public webpage and that link checks are optional, but it does not add substantial parameter-level meaning beyond the schema, especially for max_links.

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?

The description states a specific action on a specific resource: auditing one live public webpage by fetching a bounded static HTML response and running HTML, SEO/accessibility-signal, and JSON-LD syntax checks. It clearly distinguishes the scope from broader crawling and dedicated link-checking behavior by saying it does not crawl and checks links only when requested.

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?

It gives explicit when-to-use guidance tied to a user-provided live public webpage URL, plus when-not constraints such as no crawling, no JavaScript execution, no authentication, and no linked stylesheet fetching. It does not explicitly name sibling alternatives, but the exclusions and 'links only when requested' condition provide clear routing context.

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