Skip to main content
Glama
Sign In

AgentRead

by io.github.omarhassanatef
OverviewDiscussionsAdmin

Extract URL (clean Markdown)

extract_url
Read-only

Fetch a public web page and return its main content as clean Markdown with title, description, headings and extraction metadata. Removes navigation, ads, cookie banners and scripts. Does not execute JavaScript. Paid via x402 ($0.003 per successful call; the first 5 successful calls per day are free). Returns JSON (structuredContent + text) with schemaVersion, operation, requestedUrl, finalUrl, title, description, markdown, headings[{level,text}], truncated, extraction{method,statusCode,contentType,charset,redirects,bytesFetched,characters,totalCharacters,words,warnings,durationMs}.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute public http:// or https:// URL. Default ports only; no credentials; no IP literals.
includeLinksNoKeep hyperlinks and images in the Markdown (default true). When false, link text is kept as plain text.
maxCharactersNoMaximum Markdown characters to return (default 20000, max 100000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it removes navigation, ads, cookie banners, and scripts; does not execute JavaScript; includes payment details and free-call limits; and enumerates the JSON return fields. These details are fully consistent with readOnlyHint=true and openWorldHint=true.

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 front-loaded with purpose, then limitations, pricing, and return shape, with no wasted sentences. The return-field enumeration is long but justified because no output schema is provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid open-world extraction tool with no output schema, the description covers the essential behavior: what is fetched, what is stripped, JavaScript limitations, billing, and the returned JSON fields. Combined with full schema coverage and annotations, an agent has enough context to invoke it correctly.

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 the input schema already documents url, includeLinks, and maxCharacters. The description does not add parameter-specific syntax or defaults beyond what the schema provides, which is the baseline expectation when schema coverage is complete.

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 uses a specific verb and resource: fetch a public web page and return its main content as clean Markdown. It clearly distinguishes the output format from a generic extraction tool, but it does not explicitly name or differentiate the sibling tools extract_url_structured or inspect_url.

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

Usage Guidelines4/5

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

It gives clear usage context: public web pages only, with no JavaScript execution, and notes the x402 payment model. However, it does not explicitly compare when to use this tool versus extract_url_structured or inspect_url.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentRead toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources