Skip to main content
Glama

Google PageSpeed Insights for one public URL

pagespeed
Read-only

Google PageSpeed Insights for one public URL: the Lighthouse scores (performance, seo, accessibility, best-practices), the lab Core Web Vitals (FCP, LCP, CLS, TBT, Speed Index), the CrUX field data when Google has it (LCP, INP, CLS), and the top five opportunities with estimated savings. Mobile by default. A run takes 10 to 40 seconds and is cached for an hour. Keyless calls share Google's quota, so a busy moment is a 503. Price: $0.005 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttp or https URL of a public page, e.g. https://example.com/
strategyNomobile (default) or desktop
categoriesNoperformance (default), seo, accessibility, best-practices; comma-separated

Output Schema

NameRequiredDescriptionDefault
urlNo
sourceNo
finalUrlNo
strategyNo
checkedAtNo
fieldDataNo
categoriesNo
labMetricsNo
measuredAtNo
opportunitiesNo
lighthouseVersionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses latency, one-hour caching (so repeated calls may return stale data), quota-sharing failure mode (503), and the exact billing model including that failures are not charged. These are precisely the operational facts an agent needs before deciding to spend money on a call.

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?

One dense paragraph front-loads what the tool returns, then appends constraints (defaults, timing, cache, cost) in descending order of importance. No filler, no restatement of the title, and the enumerated metric lists are informative rather than padding.

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?

Output schema exists, so return values need no explanation, yet the description still summarizes them. Combined with latency, caching, failure behavior, and pricing, an agent has everything needed to invoke this correctly and interpret a 503 or a cached 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 url/strategy/categories are already documented in structured fields; the description largely restates the mobile default and adds no format or syntax detail beyond the schema. Baseline 3 is appropriate when the schema carries parameter meaning.

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?

Opens with a specific verb+resource: 'Google PageSpeed Insights for one public URL', and immediately enumerates the concrete artifacts returned (Lighthouse scores, lab CWV, CrUX field data, top five opportunities). An agent can tell exactly what this tool produces without opening the schema.

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?

Establishes the operating envelope clearly: single public URL only, mobile by default, 10-40s per run, results cached an hour, keyless quota can return 503, and a per-call price. It does not name an alternative tool or say when NOT to use it, so it falls short of the explicit routing a 5 requires.

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