Skip to main content
Glama

audit_website_geo_readiness

Audit a public website for Generative Engine Optimization readiness: check AI crawler access, /llms.txt, markdown token bloat, Content-Signal headers, and JSON-LD schema, then get deployable fixes.

Instructions

Runs a live 8-point Generative Engine Optimization (GEO) & ChatGPT Shopping audit on any public website URL: checks AI crawler access, /llms.txt, Accept: text/markdown token bloat, Content-Signal headers, and JSON-LD schema, and returns ready-to-deploy remediation snippets.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website domain or URL to inspect (e.g. 'https://example.com').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose that the audit is live, lists the checks it performs, and says it returns ready-to-deploy remediation snippets. It omits important operational behavior such as expected runtime, outbound request behavior, rate limits, error handling, and whether the target site must be publicly reachable without authentication.

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?

The definition is a single front-loaded sentence that leads with the action and then enumerates the checks and return value. It is dense but efficient, with no filler or repetition.

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 simple one-parameter tool with no output schema, the description explains the audit's scope and gives a qualitative account of the return value as remediation snippets. It could be more complete about how results are structured and operational limits, but it is adequate for correct invocation.

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% for the single required url parameter, so the schema already explains the expected input with an example. The description adds only a marginal 'public website URL' constraint and does not provide additional format or validation details beyond the schema.

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 states a specific verb and resource: it runs a live 8-point GEO and ChatGPT Shopping audit on a public website URL. It enumerates the specific checks performed, making the tool's purpose clear, but there are no sibling tools to differentiate from and the 'any public website URL' scope remains broad.

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 implied: an agent can infer this tool is used to audit a public website for AI crawler and shopping readiness. However, there is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives named for cases like private or authenticated sites.

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

Deploy Server

Other Tools