Skip to main content
Glama

webread__meta

Clean structured content from any public web page for AI agents: markdown, text, outline, links, tables, JSON-LD. GET or POST. /watch snapshots a page and detects changes for repeat monitoring. $0.01 per paid call via x402. Free /preview returns a real extraction of YOUR page. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/webread/meta

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic page URL to read
modeNoall|text|markdown|outline|links|images|tables|jsonld
limitNomax characters of main text
same_domain_onlyNolimit links to the same domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"max characters of main text"
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / mode / description
      Added value: +"all|text|markdown|outline|links|images|tables|jsonld"
    • addedInput schema / properties / same_domain_only
      Added value: +{
      +  "description": "limit links to the same domain",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / url / description
      Added value: +"public page URL to read"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  4. Changed5 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max characters of main text/markdown (200-60000)",
      -  "type": "integer"
      -}
    • removedInput schema / properties / mode
      Removed value: -{
      -  "description": "all, text, markdown, outline, links, images, tables or jsonld",
      -  "enum": [
      -    "all",
      -    "text",
      -    "markdown",
      -    "outline",
      -    "links",
      -    "images",
      -    "tables",
      -    "jsonld"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / same_domain_only
      Removed value: -{
      -  "description": "For links mode: only links on the same domain (default true)",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / url / description
      Removed value: -"Public http(s) URL to read"
    • addedInput schema / properties / url / format
      Added value: +"uri"
  5. First observed

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does add genuinely useful context: pricing at $0.01 per paid call, x402 payment via params._meta["x402/payment"], a free /preview, and the HTTP transport. It still omits error/failure behavior when payment is absent, rate limits, and whether results are cached or snapshotted.

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

Conciseness3/5

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

The capability is front-loaded, which is good, but the text then collapses pricing, payment scheme, endpoint URL and a preview promotion into one dense block. Some of it earns its place (payment requirement), while the repeated price/endpoint phrasing is redundant.

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?

There is no output schema, so the description should clarify the return shape; it names the formats but not the response structure or the difference between this tool and webread__read. For a 4-parameter, payment-gated tool with zero annotations, it is adequate but leaves key routing and failure details unstated.

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%, which sets the baseline at 3. The description echoes the extraction modes and mentions GET/POST, but adds no meaning beyond the schema for limit, same_domain_only, or how mode interacts with the other parameters.

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

Purpose3/5

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

The description states a real capability (extract markdown, text, outline, links, tables, JSON-LD from a public page), but it reads as a service blurb rather than a definition of this specific tool. With siblings named webread__read, webread__outline and webread__watch in the same family, the 'meta' name is never reconciled against those overlaps, so an agent cannot tell whether this tool reads a page or describes the service.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given relative to alternatives. It mentions '/watch' and '/preview' as endpoints without saying whether the agent should call this tool or the sibling webread__watch/webread__batch for those jobs, 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