Skip to main content
Glama
capad-xyz

searchts

by capad-xyz
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

read_url

Read any web page as clean Markdown by bypassing bot walls and JavaScript-rendered content when a direct HTTP fetch is blocked or returns empty snippets.

Instructions

Read one web page as clean Markdown, escalating through an unlocker ladder (Chrome-fingerprint fetch -> JS-rendering relay -> stealth browser) that stops at the first tier returning real content. Use this when a plain HTTP fetch is blocked (403/429, a Cloudflare/DataDome/PerimeterX bot-wall, or an 'enable JavaScript' page), the content is rendered client-side, or a previous web_search snippet was blocked, thin, or empty. Do not answer from a blocked snippet — call this tool on that URL. Returns Markdown ready to feed a model, always strips invisible/control characters, and if prompt-injection indicators are detected it fences the body as untrusted and prepends a one-line warning. Returns an 'Error: ...' string (not an exception) when every tier fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.8.0
    • removedInput schema / properties / url / description
      Removed value: -"Absolute http(s) URL of the page to read."
    • addedInput schema / properties / url / title
      Added value: +"Url"
    • addedInput schema / title
      Added value: +"read_url_toolArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "read_url_toolOutput",
+  "type": "object"
+}
  2. First observedv0.5.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses the unlocker ladder, the stop-at-first-success behavior, stripping of invisible/control characters, prompt-injection fencing with a warning line, and the fact that failures return an 'Error: ...' string rather than an exception.

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 dense but every sentence earns its place: purpose, when to use, return format, and failure behavior. It is front-loaded with the core action and then organizes supporting details logically without repetition or fluff.

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?

Given the tool's complexity, the description is complete: it covers the decision to call it, the internal escalation behavior, output format, sanitation, security handling, and error behavior. There are no major gaps an agent would need filled to select or invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter, url, and the schema provides no property description. The description compensates by explaining the URL is for a web page and by pointing the agent to 'call this tool on that URL' from a blocked snippet. It does not spell out URL formats, but the intent is clear enough for a single self-describing 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?

The description names a specific verb and resource: 'Read one web page as clean Markdown,' and clearly distinguishes itself from plain HTTP fetch and web_search snippets. However, it does not explicitly differentiate itself from sibling tools like fetch_asset or grab_site, relying on the reader to infer those boundaries.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use conditions: blocked HTTP fetch, bot-walls, client-side rendering, or a blocked/thin/empty web_search snippet. It even states a direct directive: 'Do not answer from a blocked snippet — call this tool on that URL.' This is clear, actionable routing guidance.

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

Install Server

Other Tools