Skip to main content
Glama

Black SEO Analyzer

check_page

Audit one URL immediately and return its SEO issues (schema bseoa.issue/v1: key, category, severity, message, fix_hint, docs_url). This is the fast path and the right first call for "what is wrong with this page?" - it fetches a single page and never follows links. Prefer it over start_crawl whenever the user asked about one specific page rather than a whole site, and that includes a site's homepage or bare domain ("check https://example.com/ for SEO problems") when the user did not ask for a crawl, a site audit or a number of pages. Does not count against the account's page budget; limited to 30 calls a minute. JavaScript rendering (spa) is not available on the hosted connector.

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

Input Schema

NameRequiredDescriptionDefault
spaNoRender JavaScript with a headless browser before auditing. Slower; only needed for single-page apps whose content is not in the served HTML.
urlYesAbsolute URL of the page to audit, including the scheme (https://...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare openWorldHint=true and the hint set; the description adds operational facts an agent cannot get from them: no link following, no consumption of the account's page budget, a 30 calls/minute rate limit, and the hosted-connector limitation on JavaScript rendering. These are exactly the constraints that affect call planning and retry behavior.

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?

The critical facts (single page, fast path, no link following, alternative tool) are front-loaded before secondary constraints like budget and rate limit. It is one dense paragraph with some qualifying clauses that could be tightened, but no sentence is filler.

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

Completeness5/5

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

There is no output schema, yet the description compensates by enumerating the issue record fields, and it covers the operational limits, scoping behavior, and the sibling routing decision. For a two-parameter tool, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline would be 3. The description nonetheless adds meaning beyond the schema by qualifying the spa option: rendering is unavailable on the hosted connector, which the schema's 'Render JavaScript with a headless browser' line does not disclose.

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?

The opening clause gives a specific verb+resource ('Audit one URL') and goes further to name the return payload shape ('schema bseoa.issue/v1: key, category, severity, message, fix_hint, docs_url'), so an agent knows both what it does and what it yields. It is explicitly distinguished from the start_crawl sibling, which handles site-wide work.

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

Usage Guidelines5/5

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

Usage is spelled out with a when-to-use rule ('the right first call for "what is wrong with this page?"') and an explicit alternative plus the condition that selects it ('Prefer it over start_crawl whenever the user asked about one specific page rather than a whole site'). It even closes the common ambiguity that a homepage or bare domain still counts as a single page unless the user asked for a crawl or page count.

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.