Skip to main content
Glama

Free website audit: speed, SEO and accessibility

run_website_audit
Read-only

Free audit of any public website, for questions like "why is my website slow?", "check my site speed", "audit my website SEO" or, in Portuguese, "porque é que o meu website está lento?" and "auditoria ao meu website". Runs the Google PageSpeed Insights API (https://developers.google.com/speed/docs/insights/v5/get-started) on mobile and returns performance, accessibility, best-practices and SEO scores, Core Web Vitals, the issues that weigh most on the score, missing security headers and page weight. Takes 20 to 90 seconds. Only public http(s) addresses.

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": "run_website_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website address, e.g. example.pt or https://www.example.com/page.
localeNoAnswer language: English (en) or European Portuguese (pt).en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 external dependency (Google PageSpeed Insights API v5), the strategy used (mobile), expected latency of 20–90 seconds, and the scope restriction to public http(s) URLs. The latency figure is especially valuable 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?

Structure is sound: the one-line purpose comes first, then trigger phrasing, then the technical mechanism and return contents. The multilingual query-keyword list is somewhat padded and reads like retrieval optimization rather than agent guidance, but it does not obscure the core statement.

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?

There is no output schema, so the description must carry the return-value burden and it does, enumerating every result category the caller receives. Combined with the latency estimate and URL scope limit, an agent has everything needed to call it correctly and interpret the result.

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%, so both parameters are already documented with formats and an enum, making 3 the baseline. The description adds only marginal meaning beyond that — the Portuguese example queries hint at when to set locale=pt, and the public http(s) limit reinforces the url constraint.

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 names a specific verb and resource ("audit of any public website") and enumerates exactly what is produced: performance, accessibility, best-practices and SEO scores, Core Web Vitals, top issues, missing security headers and page weight. It is unmistakable against the siblings (list_case_studies, request_contact, studio_info), none of which overlap.

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 concrete trigger phrasing ("why is my website slow?", "check my site speed", "audit my website SEO", plus Portuguese equivalents), which tells an agent the situations this tool answers. It also states a hard exclusion — only public http(s) addresses — but offers no explicit alternative tool for non-public or non-http targets.

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