Analyze a URL with PageSpeed Insights to obtain performance, accessibility, best practices, and SEO scores for mobile or desktop.
Run PageSpeed Insights analysis on a URL to get performance, accessibility, best practices, and SEO scores
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to analyze | |
| strategy | No | Device strategy (default: mobile) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It does not mention that the tool is read-only, or any permissions, rate limits, or other constraints. For a tool that likely performs a read operation, this is a significant omission.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, no wasted words, front-loaded with the core action. Every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the description states what the tool returns, there is no output schema and no mention of format or limitations. Given low complexity (2 params) and no annotations, it is minimally adequate but could specify result structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters described. The description adds no extra meaning beyond what the schema already provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (run analysis), the resource (URL), and the outputs (performance, accessibility, best practices, SEO scores). It distinguishes from sibling tool 'pagespeed_core_web_vitals' which focuses on core web vitals only.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like bing_analytics or other analysis tools. The description does not provide context for appropriate usage scenarios or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.