Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_technical_seo_composite

Audit a page's technical SEO by checking redirects, meta tags, canonicals, headings, hreflang, schema, and robots.txt, then return scored issues to fix.

Instructions

[SEO & GEO Readiness] Technical SEO audit: redirects, meta, canonical, headings, hreflang, schema, robots.txt with scored issues 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_technical_seo_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose useful behavior: results are 'scored issues', measured latency is p50 13 ms / p95 15 ms with a dated benchmark source, and it calls an external endpoint (https://seo.caelaralabs.com). It omits auth/quota requirements, whether results are cached, crawl depth/scope limits, and the shape of the scored output.

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?

Compact and front-loaded: the audit scope comes first, then scoring, latency, and endpoint. The benchmark and endpoint clauses are dense and the sentence runs on without separators, but no sentence is pure filler.

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?

For a single-URL audit with no output schema, the description should convey what comes back; 'scored issues' gestures at it without saying whether scores are per-category, what scale, or what evidence is included. Latency and the external endpoint partially compensate, but return-shape and prerequisites remain gaps.

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, and schema description coverage is 100%, so the schema already documents 'Page URL to audit' completely. The description adds nothing about URL scope (single page vs. site, http vs. https, trailing slashes), 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?

States a specific verb+resource ('Technical SEO audit') and enumerates the exact checks covered: redirects, meta, canonical, headings, hreflang, schema, robots.txt. The enumeration implicitly differentiates it from narrow siblings like hreflang_validator or redirect_chain_tracer, but the description never says so explicitly.

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 or when-not-to-use statement and no reference to alternatives, despite several siblings that overlap on individual checks (hreflang, schema.org, redirect chains, robots). An agent must infer from the check list that this is the all-in-one audit.

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