Skip to main content
Glama

webread__read

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/read

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

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. Changed7 schema fields changed
    • removedInput schema / properties / limit / maximum
      Removed value: -60000
    • removedInput schema / properties / limit / minimum
      Removed value: -200
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / mode / enum
      Removed value: -[
      -  "all",
      -  "text",
      -  "markdown",
      -  "outline",
      -  "links",
      -  "images",
      -  "tables",
      -  "jsonld"
      -]
    • removedInput schema / properties / same_domain_only
      Removed value: -{
      -  "type": "boolean"
      -}
    • removedInput schema / properties / url / format
      Removed value: -"uri"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  3. Changed7 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"Max characters of main text/markdown (200-60000)"
    • addedInput schema / properties / limit / maximum
      Added value: +60000
    • addedInput schema / properties / limit / minimum
      Added value: +200
    • removedInput schema / properties / mode / description
      Removed value: -"all, text, markdown, outline, links, images, tables or jsonld"
    • removedInput schema / properties / same_domain_only / description
      Removed value: -"For links mode: only links on the same domain (default true)"
    • removedInput schema / properties / url / description
      Removed value: -"Public http(s) URL to read"
    • addedInput schema / properties / url / format
      Added value: +"uri"
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cost ($0.01 per paid call), a free '/preview' path, the x402 payment location in params._meta, and the underlying HTTP endpoint. It omits failure behavior, rate limits, and result-size constraints, which matters for a paid call.

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?

Compact and information-dense with no filler sentences, and the core purpose leads. However, pricing, payment protocol, raw HTTP URL, and a sibling-tool pointer are packed into a single run-on block, making it harder to scan for the operational essentials.

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?

No annotations and no output schema, so the description legitimately must carry the load, and it covers output formats, cost, payment mechanics, and a monitoring alternative. It falls short on expected result shape and any limits on returned content or error conditions, which an agent making a paid call would want.

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%, so the schema already explains url, mode, limit, and same_domain_only; baseline 3 applies. The description adds a little by enumerating output representations and mentioning GET/POST, but it references params._meta['x402/payment'] which does not appear in the declared schema, so the extra detail does not cleanly map to a parameter.

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?

States a specific verb and resource: 'Clean structured content from any public web page' with concrete output formats (markdown, text, outline, links, tables, JSON-LD). It is weaker on sibling differentiation — it only contrasts with '/watch' indirectly and never distinguishes itself from webread__outline or agentkit__fetchmd, which an agent could easily confuse with a mode of this tool.

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?

Gives an implied context ('for AI agents', GET or POST) and routes repeat monitoring to '/watch', but does not say when to use this tool versus webread__outline, webread__batch, or agentkit__fetchmd. There are no explicit exclusions or prerequisites beyond the public-page restriction.

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