Skip to main content
Glama

webread__outline

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

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

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

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load, and it does disclose the operationally critical facts: paid calls cost $0.01 in USDC on Base (eip155:8453) via x402, payment goes in params._meta['x402/payment'], and /preview is free. It omits rate limits, input size caps, JS-rendered page behavior, and failure modes, which keeps it short of a 5.

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 purpose is front-loaded, which is good, but the remainder is a dense run-on mixing pricing, payment protocol, endpoint URL, and sibling mentions. The price is stated twice ('$0.01 per paid call via x402' and again as 'Price: $0.01 per call in USDC on Base'), which wastes space without adding information.

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?

For a four-parameter, no-output-schema, no-annotation tool, the description covers supported formats, cost, and the HTTP endpoint, which is most of what an agent needs to invoke it. It does not describe the shape of the returned extraction or any limits, leaving a meaningful gap for a tool whose whole value is its output.

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%, so all four parameters are already documented in the schema, including the mode value list. The description adds no meaning beyond that — it only restates the output formats that the mode field already enumerates. Baseline 3 applies.

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 opening sentence gives a specific verb and resource: extract clean structured content (markdown, text, outline, links, tables, JSON-LD) from a public web page. It is clear what the tool does in general, but it reads as a service-level blurb rather than a tool-specific one, so it never explains how it differs from webread__read or webread__batch, and the 'outline' name is not tied to a stated default behavior.

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?

There is partial routing guidance: '/watch snapshots a page and detects changes for repeat monitoring' points the agent to a monitoring alternative, and '/preview returns a real extraction of YOUR page' suggests a free trial path. However, no when-to-use or when-not-to-use conditions are given against the closest siblings (read, batch, meta), so mode selection is left 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