Skip to main content
Glama

Black SEO Analyzer

page_report

Read-only

Report everything recorded about one crawled URL: status code, redirect target, title and meta description, Open Graph tags, word count, link and asset counts, headings, TTFB, Web Vitals score, and the full issue list for that page. Use it after query_issues or issues_summary when you need the context behind a specific page's issues. It never returns the page's HTML source; to inspect markup, fetch the URL yourself.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe exact page URL as it appears in the crawl, including the scheme.
session_idNoCrawl session id from list_crawls. Omit to use the most recent crawl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful negative behavior — no HTML source is returned, markup must be fetched externally — which prevents a wasted call when an agent wants raw markup. It stops short of covering cost/pagination or what a missing page yields, but the key behavioral surprise is disclosed.

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 sentences, front-loaded with the verb and payload, and every clause carries information. The long field enumeration is justified because there is no output schema, though it reads as a checklist and could be tightened slightly without losing meaning.

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 returns and does so thoroughly, plus it names the one notable omission (HTML source). Parameters are fully covered by the schema, and the guidance anchors it to the sibling workflow, leaving little an agent needs that is missing.

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%: the url parameter already says 'exact page URL as it appears in the crawl, including the scheme', and session_id already documents the default-to-latest behavior. The description only echoes scoping ('one crawled URL') without adding syntax, format, or edge-case guidance beyond the schema, so baseline 3 applies.

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 description opens with a specific verb and resource ('Report everything recorded about one crawled URL') and then enumerates the exact payload: status code, redirect target, title/meta, Open Graph, word count, link/asset counts, headings, TTFB, Web Vitals, issue list. That enumeration makes it unmistakable against siblings like query_issues or issues_summary, which return issue rows rather than per-page context.

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?

It states a concrete workflow position ('Use it after query_issues or issues_summary when you need the context behind a specific page's issues'), which tells the agent both the trigger and the ordering relative to named siblings. It also gives an explicit when-not plus alternative: 'It never returns the page's HTML source; to inspect markup, fetch the URL yourself.'

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.