Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_schema_org_validator

Extract and validate JSON-LD and microdata structured data from a page URL to verify schema markup and improve SEO/GEO readiness.

Instructions

[SEO & GEO Readiness] Extract and validate JSON-LD / microdata structured data on a page 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_schema_org_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It adds latency benchmarks (p50 13 ms, p95 15 ms) and the backing endpoint, which is genuinely useful, but says nothing about whether the tool fetches the live page over the network, how it handles unreachable pages or missing structured data, or whether there are auth/rate constraints.

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?

Two short sentences, with the capability front-loaded ahead of the benchmark/endpoint metadata. It is slightly run-on ("...on a page Measured p50...") and the benchmark citation is boilerplate, but nothing is padded.

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?

With no output schema and no annotations on a validation tool, the description should indicate what the result contains (detected schema types, validation errors, pass/fail). It never does, and it also leaves the network-fetch behavior unstated, so the agent cannot anticipate the response shape or failure modes.

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?

Only one parameter (url) and schema description coverage is 100%, so the schema already documents it. The description adds no detail about URL format, whether redirects or non-HTML resources are handled, so baseline 3 applies.

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 gives a specific verb pair ("Extract and validate") and a specific resource ("JSON-LD / microdata structured data on a page"), and the "[SEO & GEO Readiness]" tag situates it in a family. It stops short of naming a sibling it differs from (e.g. the geo-readiness composite or technical SEO composite), so an agent must infer the boundary from the resource noun alone.

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?

There is no when-to-use guidance, no statement of prerequisites (does the page need to be publicly reachable?), and no routing to alternatives such as caelara_seo_geo_readiness_composite or caelara_seo_technical_seo_composite. The SEO tag only weakly implies context.

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