Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_hreflang_validator

Validate hreflang annotations on a page, including language codes, x-default, self-reference, and optional reciprocal return links, to catch SEO alternate-language tagging errors.

Instructions

[SEO & GEO Readiness] Validate hreflang annotations: codes, x-default, self-reference and optional return links Measured p50 13 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://seo.caelaralabs.com.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "caelara_seo_hreflang_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL
check_return_linksNoVerify reciprocal links on up to 5 alternates (true/false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description usefully adds measured p50/p95 latency and discloses that it calls an external service. It does not explicitly establish read-only behavior, whether the target page is fetched remotely, URL privacy implications, or authentication and failure behavior.

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 purpose is front-loaded and the overall definition is compact. Missing punctuation between “return links” and “Measured” creates a run-on, and the dated benchmark citation adds some selection-time noise.

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

Completeness3/5

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

The check scope and fully described two-parameter schema are sufficient for a basic invocation, with endpoint and latency supplying useful operational context. Because there is no output schema or annotation support, the lack of information about result structure, errors, and public fetchability remains a meaningful gap.

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?

Schema description coverage is 100%, and the schema already explains both inputs, including the five-alternate cap for return-link checks. The description’s “optional return links” adds little beyond that schema and provides no additional URL format or accessibility requirements.

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?

“Validate hreflang annotations” gives a specific verb and resource, while “codes, x-default, self-reference and optional return links” makes the validation scope concrete. It does not explicitly distinguish this focused check from broader SEO or composite siblings.

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

Usage Guidelines4/5

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

The “[SEO & GEO Readiness]” label and detailed check list provide clear context for auditing a page’s hreflang implementation, optionally including reciprocal links. There is no when-not guidance or named alternative for broader technical SEO audits or other markup validation.

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

Deploy Server

Other Tools