Skip to main content
Glama
ruslanlap

PageSpeed Insights MCP Server

by ruslanlap

get_recommendations

Analyze a web page to receive prioritized performance recommendations with actionable fixes across multiple categories like performance, accessibility, and SEO.

Instructions

Generate smart performance recommendations with priority scoring and actionable fixes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to analyze for recommendations
strategyNoAnalysis strategymobile
categoryNoCategories to analyze for recommendations
localeNoLocale for resultsen
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only describes output (prioritized recommendations) but does not mention side effects, required permissions, rate limits, or whether the operation is read-only. This is a significant gap.

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?

Description is a single sentence of 11 words, front-loading the core purpose without any fluff. Every part is meaningful.

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

Completeness2/5

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

With no output schema and 4 parameters (1 required), the description is too brief. It fails to explain return structure, how priority scoring works, or what constitutes actionable fixes. More detail is needed for an agent to use it correctly.

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?

Input schema has 100% parameter description coverage, so baseline is 3. The tool description adds no additional context about how parameters affect recommendations or priority scoring. It does not improve 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?

Description clearly states the tool generates performance recommendations with priority scoring and actionable fixes. However, it does not differentiate from sibling tools like 'get_full_audit' or 'analyze_page_speed', which may also provide recommendations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides no guidance on when to use this tool vs. alternatives. No mention of prerequisites, context, or conditions that make this tool preferable over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ruslanlap/pagespeed-insights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server