Skip to main content
Glama

Seahawk Media

Check a website

check_website
Read-onlyIdempotent

Run Seahawk's free website checker on any public page: HTTP status, HTTPS and redirect, security headers, SEO basics (title, description, headings, canonical, robots), WordPress detection with theme and plugins, and optionally the status of every link on the page. Same as https://seahawkmedia.com/tools/seo-checker/.

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_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA public website address, e.g. example.com or https://example.com/page/.
check_linksNoAlso check each link on the page (slower).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real context beyond that: it is a free external check, restricted to public pages, enumerates the categories of results, and flags that full link checking is an optional extra pass. It does not mention rate limits or reliability caveats, and there is no output schema to explain result shape.

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?

A single front-loaded sentence with the enumerated checks in a compact list, ending with an external reference URL for expectation-setting. The URL is mildly redundant but arguably useful; no filler otherwise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing results, and its enumeration of checked categories largely does that. Remaining gaps are minor: no indication of response format or how failures/blocked pages are reported.

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 both parameters are already documented, including the 'slower' note on check_links. The description restates that link checking is optional and reiterates the public-page constraint for url, but adds no format or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Run Seahawk's free website checker on any public page') and then enumerates exactly what is inspected: HTTP status, HTTPS/redirect, security headers, SEO basics, WordPress detection, and optional link status. An agent can immediately distinguish this from siblings like test_page_speed or get_page.

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 only implied: 'any public page' signals the scope, and 'optionally the status of every link' hints at when to enable the slower check. There is no explicit when-to-use-this-vs-alternative guidance (e.g., vs test_page_speed for performance), leaving routing to inference.

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