Skip to main content
Glama
AutomateLab-tech

automatelab-ai-seo

Official
by AutomateLab-tech
OverviewSchemaRelated ServersScoreDiscussions(1)
TypeScript
Remote

Score AI Overview eligibility

score_ai_overview_eligibility
Read-onlyIdempotent

Evaluate any URL's likelihood of appearing in Google AI Overviews. Get a 0-100 score plus six factor subscores: semantic completeness, structured data, E-E-A-T, entity density, freshness, and technical hygiene.

Instructions

Score a page's probability of appearing in Google AI Overviews. Returns an overall 0-100 score plus six factor subscores: semantic completeness, structured data, E-E-A-T signals, entity density, freshness, and technical hygiene.

Read-only. One HTTP GET.

Deterministic, rule-based scoring derived from published 2025-2026 AI-Overview correlation studies. No LLM calls. Same URL returns the same score on repeated runs.

When to use: AI-Overview-specific prioritization. For a multi-dimensional audit that includes this scoring plus everything else, use audit_page. For citation-worthiness of a specific text passage (rather than a URL ranking probability), use score_citation_worthiness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic URL to score. The tool fetches the URL once and runs deterministic, rule-based scoring across six factors (semantic completeness, structured data, E-E-A-T signals, entity density, freshness, technical hygiene) using published 2025-2026 correlation studies. No LLM calls. Read-only HTTP GET.
respect_robotsNoIf true (default), respect robots.txt before fetching. Set false only for auditing your own site where you've intentionally blocked crawlers.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
factorsYesPer-factor 0-100 subscores.
fetched_atYes
top_improvementsYes
overall_eligibility_scoreYes

Schema Changelog

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

  1. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "factors": {
+      "additionalProperties": false,
+      "description": "Per-factor 0-100 subscores.",
+      "properties": {
+        "eeat_signals": {
+          "type": "number"
+        },
+        "entity_density": {
+          "type": "number"
+        },
+        "freshness": {
+          "type": "number"
+        },
+        "semantic_completeness": {
+          "type": "number"
+        },
+        "structured_data": {
+          "type": "number"
+        },
+        "technical_hygiene": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "semantic_completeness",
+        "structured_data",
+        "eeat_signals",
+        "entity_density",
+        "freshness",
+        "technical_hygiene"
+      ],
+      "type": "object"
+    },
+    "fetched_at": {
+      "type": "string"
+    },
+    "overall_eligibility_score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    "top_improvements": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "factor": {
+            "type": "string"
+          },
+          "suggestion": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "factor",
+          "suggestion"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "fetched_at",
+    "overall_eligibility_score",
+    "factors",
+    "top_improvements"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / respect_robots / description
      Added value: +"If true (default), respect robots.txt before fetching. Set false only for auditing your own site where you've intentionally blocked crawlers."
    • addedInput schema / properties / url / description
      Added value: +"Public URL to score. The tool fetches the URL once and runs deterministic, rule-based scoring across six factors (semantic completeness, structured data, E-E-A-T signals, entity density, freshness, technical hygiene) using published 2025-2026 correlation studies. No LLM calls. Read-only HTTP GET."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds key traits: 'Read-only. One HTTP GET.', 'Deterministic, rule-based scoring... No LLM calls.', 'Same URL returns the same score on repeated runs.' No contradictions with annotations.

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 well-structured: purpose first, then output details, then behavioral traits, then usage guidance. Every sentence adds unique value with no redundancy. Front-loaded with the most critical information.

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

Completeness5/5

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

Given the tool has 2 parameters with full schema coverage, an output schema (mentioned), and annotations covering safety, the description is complete. It explains what the tool does, what it returns (overall score + six subscores), and how to choose it over siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (both parameters documented). The main description adds value by explaining the URL parameter's behavior ('fetches the URL once and runs deterministic...') and providing usage guidance for respect_robots ('Set false only for auditing your own site where you've intentionally blocked crawlers.').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Score') and resource ('page's probability of appearing in Google AI Overviews'). It distinguishes from siblings by naming audit_page and score_citation_worthiness as alternatives for different use cases.

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

Usage Guidelines5/5

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

Explicitly states when to use ('AI-Overview-specific prioritization') and when not, with named alternatives: 'use audit_page' for multi-dimensional audit, 'use score_citation_worthiness' for passage citation-worthiness.

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/AutomateLab-tech/ai-seo-mcp'

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