web-scraper
Server Details
Web scraper for agents: fetch any URL as clean markdown (headings, links). x402 for JS rendering.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- agishub/agishub-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
A single tool name follows a clear verb pattern (extract) and is consistent internally.
One tool is minimal for a web scraper; while it covers basic use, it lacks separate operations for tasks like listing links or handling pagination.
The tool covers fetching and extracting main content, but missing features like raw HTML access, custom selectors, and pagination handling leave significant gaps.
Available Tools
1 toolextractAInspect
Agis Web Scraper — Fetch any public web page and return its main content as clean markdown (title, description, headings, links, lists). Optional JavaScript rendering (render:true) for SPAs / JS-heavy pages. Ideal for RAG and agents that need to read a URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Full http/https URL of the page to extract. | |
| render | No | Render JavaScript with a headless browser before extracting (default false). Enable for SPAs / JS-heavy pages that return empty content otherwise. Slower. | |
| max_chars | No | Truncate the markdown to at most this many characters (sets truncated:true). | |
| include_links | No | Keep hyperlinks in the markdown output (default true). | |
| include_images | No | Keep images as markdown (default false). |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions optional JavaScript rendering, truncation, and markdown structure, but does not disclose error behavior, rate limits, or that it is read-only (implied by 'fetch'). Some behavioral traits are missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences that are concise and front-loaded with purpose. The second sentence could be slightly restructured for readability, but it effectively conveys key features without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, but the description specifies the return format (clean markdown with title, description, headings, links, lists). It covers parameter effects and use cases. Missing error handling details, but adequate for a fetch tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds value by explaining why render is needed ('SPAs / JS-heavy pages') and what max_chars does ('sets truncated:true'), going beyond the schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches public web pages and returns main content as clean markdown. It specifies verb 'fetch' and resource 'public web page', with no sibling tools requiring differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says 'Ideal for RAG and agents that need to read a URL', providing context for use. It also hints at when to enable rendering for SPAs/JS-heavy pages, but lacks explicit exclusion criteria or alternative tools (none exist here).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!