automatelab-ai-seo

Official

by AutomateLab-tech

Overview Schema Related Servers Score Discussions(1)

TypeScript

Remote

Check technical HEAD signals

check_technical

Read-onlyIdempotent

Audit a webpage's HEAD section for AI-crawler technical signals including HTTPS, canonical, OpenGraph, Twitter Card, hreflang, noindex, and title-H1 alignment.

Instructions

Audit a page's HEAD section for technical signals relevant to AI crawlers: HTTPS, canonical, OpenGraph, Twitter Card, hreflang, noindex, and title-vs-H1 hygiene.

Read-only. One HTTP GET, inspects HEAD only (body is not parsed).

Deterministic, rule-based; no LLM.

When to use: when you specifically need HEAD-tag audit findings. For the full page including schema and AI-Overview scoring, use audit_page. For canonical-only, use audit_canonical.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public URL to audit. The tool fetches the URL once and inspects HEAD-section signals: HTTPS, canonical, OpenGraph, Twitter Card, hreflang, noindex, title length and overlap with H1. Body content is not parsed. Read-only HTTP GET.
`respect_robots`	No	If 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

Name	Required	Description
`h1`	Yes	First H1 text.
`url`	Yes
`https`	Yes	Whether the URL is served over HTTPS after redirects.
`title`	Yes	Page title text.
`og_url`	Yes	OpenGraph og:url, if present.
`noindex`	Yes	Whether meta robots includes noindex.
`findings`	Yes
`canonical`	Yes	Canonical link href, if present.
`fetched_at`	Yes

Schema Changelog

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

Changed1 schema field changedv1.0.0Jul 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "canonical": {
+      "description": "Canonical link href, if present.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "fetched_at": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "description": "Finding category - which AI-SEO dimension it relates to.",
+            "enum": [
+              "schema",
+              "robots",
+              "technical",
+              "freshness",
+              "structure",
+              "authority",
+              "presence",
+              "sitemap",
+              "llms_txt",
+              "citation",
+              "evidence",
+              "trust",
+              "entity",
+              "content"
+            ],
+            "type": "string"
+          },
+          "estimated_impact": {
+            "description": "Estimated impact on AI citation probability when resolved.",
+            "enum": [
+              "high",
+              "medium",
+              "low"
+            ],
+            "type": "string"
+          },
+          "failure_signal": {
+            "description": "Falsifiability: the observable signal that would prove the fix did NOT work.",
+            "type": "string"
+          },
+          "fix": {
+            "description": "Concrete, copy-pasteable fix.",
+            "type": "string"
+          },
+          "leading_indicator": {
+            "description": "Falsifiability: the leading indicator to monitor to confirm the fix is landing.",
+            "type": "string"
+          },
+          "message": {
+            "description": "Human-readable description of the issue.",
+            "type": "string"
+          },
+          "severity": {
+            "description": "Triage priority: critical blocks AI citation, warning hurts probability, info is nice-to-have.",
+            "enum": [
+              "critical",
+              "warning",
+              "info"
+            ],
+            "type": "string"
+          },
+          "where": {
+            "description": "Location of the issue (CSS selector, JSON-LD path, robots.txt line, or 'page-level').",
+            "type": "string"
+          }
+        },
+        "required": [
+          "severity",
+          "category",
+          "where",
+          "message",
+          "fix"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "h1": {
+      "description": "First H1 text.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "https": {
+      "description": "Whether the URL is served over HTTPS after redirects.",
+      "type": "boolean"
+    },
+    "noindex": {
+      "description": "Whether meta robots includes noindex.",
+      "type": "boolean"
+    },
+    "og_url": {
+      "description": "OpenGraph og:url, if present.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Page title text.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "fetched_at",
+    "https",
+    "canonical",
+    "og_url",
+    "noindex",
+    "title",
+    "h1",
+    "findings"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.1.2May 15, 2026

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 audit. The tool fetches the URL once and inspects HEAD-section signals: HTTPS, canonical, OpenGraph, Twitter Card, hreflang, noindex, title length and overlap with H1. Body content is not parsed. Read-only HTTP GET."

First observedv0.1.0May 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses behavioral traits beyond annotations: read-only (one HTTP GET), only inspects HEAD, deterministic/rule-based, no LLM. 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?

Four well-structured sentences: purpose, behavioral traits, deterministic nature, usage guidelines. No redundancy, every sentence adds value.

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 moderate complexity and presence of an output schema, the description provides all necessary context for correct agent selection and invocation, including what is checked and when to use alternatives.

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 coverage is 100%, but the description adds value by elaborating on the URL parameter's scope (all the signals inspected) and providing context for the `respect_robots` parameter's usage.

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 ('Audit') and resource ('a page's HEAD section for technical signals'), listing the exact signals checked. It distinguishes from siblings by noting what it does not cover, such as schema or full page audits.

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 provides a 'When to use' section that specifies the appropriate context (HEAD-tag audit) and names alternative tools (audit_page, audit_canonical) for related but different tasks.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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