Skip to main content
Glama
s3eidat

S3eidat Tools MCP

by s3eidat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Fetch a web page as Markdown

ai_web_fetch
Read-onlyIdempotent

Fetch an HTTP/HTTPS page and convert its main article into clean Markdown with title, byline, final URL, and word count. Target content with a CSS selector or save the Markdown to a file.

Instructions

Fetch a web page (http/https) and return its readable content as clean Markdown, with title, byline, final URL after redirects and a word count. Uses Mozilla Readability to keep the main article (falls back to the whole page), or a CSS "selector" you give. Respects robots.txt (refuses pages disallowed for the s3eidat-tools-mcp user agent), only reads HTML and text responses, stops at 5 MB and 20 seconds, follows up to 5 redirects, and refuses private, local and loopback addresses unless allowPrivate is true. Does not run JavaScript, so pages that build their content in the browser may come back nearly empty. Inline Markdown is cut at maxChars (default 200k); "output" saves it to a file.

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to fetch (http:// or https://).
outputNoWrite the Markdown to this file (or folder ending in "/") and return its path instead of the inline text.
maxCharsNoCut the inline Markdown after this many characters, with a note (a file written with "output" is never cut). Default 200000.
readableNoKeep only the main content (default true). False converts the whole page body.
selectorNoCSS selector: convert only the matching elements instead of the Readability main content.
allowPrivateNoAllow private, local and loopback hosts (e.g. a dev server on localhost). Default false.
includeLinksNoKeep links (made absolute) and images. False turns links into plain text and drops images.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations with concrete operational limits: 5 MB and 20 second caps, up to 5 redirects, SSRF protection on private/local/loopback addresses, robots.txt enforcement for the named user agent, and Readability-with-fallback behavior. It also discloses the key failure mode (JS-built pages yield near-empty output) and the truncation semantics of maxChars.

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?

Front-loaded with purpose and output shape, then a dense but purposeful run of constraints — every clause carries an operational fact. It is a single long paragraph rather than a scannable structure, which costs a point, but there is no filler.

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 7-parameter open-world fetch tool with no output schema, the description covers return shape (title, byline, final URL, word count, inline Markdown), truncation, redirects, timeouts, size limits, and safety refusals. An agent has everything needed to call it correctly and anticipate failures.

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 every parameter is already documented in the schema, including defaults for maxChars, readable, and allowPrivate. The description reinforces selector, maxChars, output, and allowPrivate but adds no syntax or format detail beyond what the schema states; baseline 3 applies.

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

Purpose5/5

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

The first clause names a specific verb and resource — fetch a web page over http/https and return its readable content as Markdown — and enumerates the returned fields. It is clearly distinguishable from file-oriented siblings like ai_html_to_markdown, which operate on HTML you already have rather than fetching a live 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 explicit operating conditions and exclusions: no JavaScript execution so browser-rendered pages may come back empty, robots.txt refusals, non-HTML responses rejected, and allowPrivate needed for localhost. It doesn't name a sibling tool to use instead when a page is JS-rendered, so an agent gets clear context but no explicit alternative.

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

Deploy Server

Other Tools