Skip to main content
Glama

validate_all_seo

Run SEO analysis using PageSpeed Insights to validate website optimization for search engines through automated testing.

Instructions

Run SEO analysis using PageSpeed Insights (includes Lighthouse SEO).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • Core handler function implementing validate_all_seo tool logic by running PageSpeed Insights SEO analysis.
    export async function runAllSEO(url: string): Promise<AllSEOResult> {
      const results: AllSEOResult = {
        url,
        timestamp: new Date().toISOString(),
        summary: {
          tools_run: [],
        },
      };
    
      // Use PageSpeed Insights (includes Lighthouse SEO)
      const pagespeed = await analyzePageSpeed(url, { categories: ['seo'] });
      results.pagespeed_seo = pagespeed;
    
      if (pagespeed.success) {
        results.summary.tools_run.push('pagespeed');
        results.summary.seo_score = pagespeed.seo_score;
      }
    
      return results;
    }
  • MCP server dispatcher handler that validates input and delegates to runAllSEO.
    case 'validate_all_seo': {
      const validatedArgs = AllSEOArgsSchema.parse(args);
      const result = await runAllSEO(validatedArgs.url);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • index.ts:260-270 (registration)
    Tool registration definition including name, description, and input schema.
    {
      name: 'validate_all_seo',
      description: 'Run SEO analysis using PageSpeed Insights (includes Lighthouse SEO).',
      inputSchema: {
        type: 'object',
        properties: {
          url: { type: 'string' },
        },
        required: ['url'],
      },
    },
  • Zod schema used for input argument validation in the tool handler.
    const AllSEOArgsSchema = z.object({
      url: z.string().url(),
    });
  • TypeScript interface defining the output structure of the SEO validation result.
    export interface AllSEOResult {
      url: string;
      timestamp: string;
      pagespeed_seo?: PageSpeedResult;
      summary: {
        tools_run: string[];
        seo_score?: number;
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool used (PageSpeed Insights with Lighthouse SEO) but doesn't describe key traits like whether it's a read-only operation, potential rate limits, authentication needs, or what the analysis entails (e.g., report format, execution time). This leaves significant gaps for an agent to understand the tool's behavior.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded and appropriately sized for its purpose, earning a high score for 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?

Given the tool's complexity (SEO analysis), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what the analysis returns, potential errors, or behavioral aspects, making it inadequate for an agent to fully understand the tool's context and usage.

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 input schema has 1 parameter with 0% description coverage, so the description must compensate. It implies the parameter is a URL for analysis but doesn't specify format constraints (e.g., must be a valid HTTP/HTTPS URL) or provide any additional semantic details. This adds minimal value beyond what the schema name 'url' suggests, meeting the baseline for low coverage.

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 action ('Run SEO analysis') and the resource/tool used ('using PageSpeed Insights (includes Lighthouse SEO)'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'validate_comprehensive' or 'validate_all_performance', which might also involve SEO aspects, so it doesn't reach the highest score.

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 use this tool versus alternatives, such as 'validate_comprehensive' or 'validate_all_performance', nor does it mention any prerequisites or exclusions. It implies usage for SEO analysis but lacks explicit context for tool selection.

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/cordlesssteve/webby-mcp'

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