Skip to main content
Glama

Web Page Report - clean Markdown + Open Graph metadata in one call

web_page_report
Read-onlyIdempotent

One call for one URL: the main content as clean Markdown for LLMs (word count, language, author) plus title, description, Open Graph image, site name and favicon. Respects robots.txt. ~1-3 s. Free: 25 calls/day per IP. Paid: $0.004 per call via x402 at https://radarbg.com/x402/web-page-report.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://en.wikipedia.org/wiki/Web_scraping"
    },
    "name": "web_page_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL, e.g. https://en.wikipedia.org/wiki/Web_scraping
maxCharsNoCut the Markdown after this many characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the supplied readOnly, openWorld, and idempotent annotations, the description discloses robots.txt compliance, expected latency, free daily quota, and paid x402 pricing. These are meaningful behavioral traits for an agent deciding whether and how to call the tool, though error or empty-content behavior is not covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the core capability, and then covers the key operational details without filler. Every sentence contributes either functional or behavioral information.

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 usefully lists the returned content and metadata fields, and it covers safety, latency, and quota context. It is largely complete for a simple single-URL read tool, though it omits explicit failure or empty-page behavior.

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%, and the schema already documents both the required url and optional maxChars parameters. The description adds only that the tool operates on one URL, so it does not add parameter meaning beyond the structured schema.

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 operation: fetch one URL and return its main content as clean Markdown plus Open Graph metadata. The resource and output are clear, but it does not explicitly distinguish this tool from related siblings such as web_read or website_report.

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?

The phrase 'One call for one URL' implies single-page extraction, and the quota/payment details provide practical operating context. However, it gives no explicit when-to-use guidance versus alternatives and no exclusions or prerequisites beyond the rate limits.

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