Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_broken_link_scanner

Scan a page's outbound and internal links for 4xx/5xx responses and dead hosts to identify broken links before they harm SEO and user experience.

Instructions

[SEO & GEO Readiness] Check outbound and internal links on a page for 4xx/5xx and dead hosts 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_broken_link_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL
max_linksNoMax links to check 1-40 (default 25)

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, the description carries the full burden, and it does disclose the scan scope (outbound + internal links, 4xx/5xx, dead hosts) and latency figures. It omits whether redirects are followed, whether checks are concurrent, auth/rate-limit expectations, and the response shape, so it is only partially adequate.

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?

Short and front-loaded: family tag, then purpose, then performance, then endpoint. The benchmark citation is somewhat promotional but conveys useful latency context; nothing is redundant.

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 simple two-parameter read tool with no output schema and no annotations, the description should say what comes back (per-link statuses? counts?) and any limits on scope. It covers purpose and check scope but leaves return values and operational constraints unstated.

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%, so the schema already documents both 'url' and 'max_links' including the 1-40 range and default of 25. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 ('Check') and resource ('outbound and internal links on a page') plus the exact failure classes detected (4xx/5xx, dead hosts). It is distinguishable from siblings like the redirect chain tracer or sitemap crawler, though it never names an alternative.

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 guidance and no routing to alternatives. The '[SEO & GEO Readiness]' tag only implies it belongs to a family of audits; an agent must guess whether to run this or the technical-SEO composite first.

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