Skip to main content
Glama
SEO Audit MCP

SEO Audit MCP

by Nexariza-AI

Check the links on a page

check_links

Detect broken, redirected, and slow links by fetching a page and checking link HTTP statuses for SEO audits.

Instructions

Fetches a page and checks the HTTP status of its links. Reports broken (4xx/5xx/unreachable), redirected and slow links.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page whose links to check
limitNoMaximum links to check (default 60)
externalOnlyNoOnly check links to other sites

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 important behavioral fact that the tool performs network fetches of both the page and its links, plus how results are categorized. It does not cover what happens if the source page itself fails to load, what 'slow' means (no threshold), whether checks are rate-limited or concurrent, or whether results include the URL list.

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 tightly packed sentences with zero filler, and the core action plus the reported outcome classes are front-loaded. It could be marginally better by separating the reporting detail from the action statement.

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 three-parameter network tool with no output schema and no annotations, the description covers the action and the categories of findings but not the shape of the result set, the 'slow' cutoff, or failure behavior for the target page. Adequate to call correctly, but not complete.

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%, so all three parameters (url, limit, externalOnly) are already documented with types, a max of 200, and a default of 60. The description adds no further meaning about parameters, so the baseline of 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 states a specific verb and resource ("Fetches a page and checks the HTTP status of its links") and names the result categories (broken 4xx/5xx/unreachable, redirected, slow). It is clearly distinct from a page audit or site-file check in intent, though it never explicitly contrasts itself with the sibling tools.

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?

Usage is implied by the verb and the reported outcomes — an agent can infer 'use this to find broken links on a single page'. There is no explicit when-to-use/when-not, no mention of the sibling alternatives (audit_page vs check_site_files), and no prerequisites such as whether the URL must be publicly reachable.

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