Skip to main content
Glama
danielsogl

Lighthouse MCP

by danielsogl
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Get SEO Analysis

get_seo_analysis
Read-only

Perform an SEO audit on a given website URL, with options to select device type and include detailed metrics and recommendations.

Instructions

Get SEO analysis and recommendations for a website

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to audit
deviceNoDevice to emulate (default: desktop)desktop
includeDetailsNoInclude detailed metrics and recommendations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
summaryYes
recommendationsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.27
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "audits": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "description": {
+                "type": "string"
+              },
+              "displayValue": {
+                "type": "string"
+              },
+              "score": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "title",
+              "score",
+              "displayValue"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "fetchTime": {
+          "type": "string"
+        },
+        "includeDetails": {
+          "type": "boolean"
+        },
+        "seoScore": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "seoScore",
+        "fetchTime",
+        "includeDetails"
+      ],
+      "type": "object"
+    },
+    "recommendations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "summary",
+    "data"
+  ],
+  "type": "object"
+}
  2. Addedv1.0.26
  3. Removedv1.0.1
  4. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds no further behavioral context such as rate limits, time expectations, or the nature of external fetches, offering minimal value beyond the annotations.

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?

The description is a single, front-loaded sentence that efficiently states the core purpose. It is appropriately concise for a tool whose parameters and return format are fully specified in the schema.

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?

Given the large set of specialized audit siblings, the description is thin on context for selection. It doesn't mention that this provides a comprehensive overview or when to prefer it over targeted tools, and it omits any note about output shape (though the output schema covers that). The lack of usage guidance undermines completeness.

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?

The schema provides full descriptions for all three parameters at 100% coverage. The description adds no extra meaning, so the baseline of 3 applies. Nothing is lacking in terms of parameter documentation.

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?

The description clearly states the tool retrieves SEO analysis and recommendations for a website, using a specific verb and resource. While it doesn't explicitly contrast with sibling audit tools, the name and resource make it distinct from performance, accessibility, and security-specific tools.

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?

The description provides no guidance on when to choose this tool over alternative audit or metric tools. An agent must infer from the name that it covers general SEO, with no explicit exclusions or references to 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/danielsogl/lighthouse-mcp-server'

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