Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

technical_seo_composite

Technical SEO audit: redirects, meta, canonical, headings, hreflang, schema, robots.txt with scored issues. Use when you need to run a technical SEO audit of one page: redirects, meta tags, canonical, headings, hreflang, schema and robots.txt, with scored issues. Example input: ?url=https://example.com/pricing.

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": "technical_seo_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the audit's coverage and that results come back as 'scored issues', which is real behavioral signal. However, it says nothing about whether the URL is fetched live, how failures (404, timeouts, unreachable hosts) are reported, or what the scoring scale means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description duplicates itself almost verbatim: the check list ('redirects, meta, canonical, headings, hreflang, schema and robots.txt') and the phrase 'scored issues' each appear twice across two sentences. The redundant second sentence eats roughly half the text without adding information.

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 composite tool that bundles seven checks with no output schema, the definition covers what is inspected and that issues are scored, which is the core. It stops short of explaining the response structure or how overlapping per-signal siblings relate to this aggregate call, leaving meaningful gaps for a multi-check tool.

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 coverage is 100% for the single 'url' parameter, so the schema already documents it, and the baseline of 3 applies. The example input string shows the expected URL shape but adds no constraint detail such as scheme requirements or whether non-HTML resources are allowed.

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 ('run a technical SEO audit of one page') and enumerates the checks performed (redirects, meta, canonical, headings, hreflang, schema, robots.txt). The 'one page' scope is a useful differentiator against crawl-style siblings, but it never names which sibling to prefer for deep single-signal checks like hreflang or redirect tracing.

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

Usage Guidelines3/5

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

The clause 'Use when you need to run a technical SEO audit of one page' gives a usage context, but it largely restates the purpose rather than adding selection logic. There is no when-not guidance and no mention of the narrower sibling validators, so an agent must infer that this is the bundle option.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources