Skip to main content
Glama

web-scraper

by com.agishub

extract

Fetch any public web page and return its main content as clean, token-efficient Markdown (title, description, headings, links, lists). Set render:true to execute JavaScript first for single-page apps or JS-heavy pages that would otherwise come back empty. Built for RAG and for agents that need to read the contents of a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull http/https URL of the page to extract.
renderNoRender JavaScript with a headless browser before extracting (default false). Enable for SPAs / JS-heavy pages that return empty content otherwise. Slower.
max_charsNoTruncate the markdown to at most this many characters (sets truncated:true).
include_linksNoKeep hyperlinks in the markdown output (default true).
include_imagesNoKeep images as markdown (default false).

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions Markdown output and render behavior but lacks details on error handling, rate limits, or access restrictions.

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?

Two sentences, front-loaded with core purpose, second sentence explains key parameter. No wasted words.

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?

Comprehensive for a web extraction tool with no siblings and no output schema. Covers main behavior and key parameter, though error handling and size limits are omitted.

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?

Schema coverage is 100%, baseline 3. Description adds meaning by explaining render's purpose with performance trade-off and that max_chars sets truncated:true, exceeding schema detail.

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?

Description clearly states the tool fetches any public web page and returns main content as Markdown, listing included elements. Verb+resource is specific and unambiguous.

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?

Provides guidance on when to use render:true (SPAs/JS-heavy pages) and that it's slower. No sibling tools to differentiate, but context is clear.

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

All web-scraper toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

With only one tool, there is no possibility for confusion between tools. The tool 'extract' has a clear and distinct purpose.

Naming Consistency5/5

The single tool name 'extract' follows a verb pattern, which is consistent and appropriate for its action.

Tool Count3/5

One tool for web scraping is somewhat thin, as a typical scraping workflow might involve multiple steps. However, the tool is comprehensive and covers the core use case, making it borderline appropriate.

Completeness4/5

The tool covers the primary need of fetching web pages and converting to Markdown, including JS rendering. Minor gaps like authentication or element-specific extraction exist but are workable.

Resources