Skip to main content
Glama
ruslanlap

PageSpeed Insights MCP Server

by ruslanlap

get_recommendations

Analyze a URL to receive prioritized, actionable recommendations for improving performance, accessibility, best practices, 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?

Minimal behavioral disclosure: no mention of authentication, rate limits, side effects, or output format. Without annotations, description carries full burden but fails to provide key behavioral traits.

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?

Single sentence, 9 words, front-loaded with the core function. Efficient, though could expand slightly on key details without losing conciseness.

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?

Incomplete for a tool with 4 parameters, no output schema, and many sibling tools. Lacks differentiation, return value explanation, and behavioral constraints.

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 parameters are documented. Description adds no extra meaning beyond what's in the schema, meeting baseline.

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 tool generates performance recommendations with priority scoring and actionable fixes. However, it does not differentiate from siblings like get_performance_summary or analyze_page_speed.

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?

No guidance on when to use this tool vs alternatives. Missing context about prerequisites or appropriate scenarios.

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