Skip to main content
Glama
AutomateLab-tech

automatelab-ai-seo

Official

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
NameRequiredDescriptionDefault
urlYesPublic 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_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
h1YesFirst H1 text.
urlYes
httpsYesWhether the URL is served over HTTPS after redirects.
titleYesPage title text.
og_urlYesOpenGraph og:url, if present.
noindexYesWhether meta robots includes noindex.
findingsYes
canonicalYesCanonical link href, if present.
fetched_atYes
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.

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