Skip to main content
Glama
maccydee

cute-web-scraper

by maccydee

fetch_page

Fetch any web page and get clean markdown with metadata. Renders JavaScript, waits for elements, strips navigation, and even extracts PDFs.

Instructions

Fetch one web page and return its content as clean markdown with metadata. Set js_render=true for pages that need JavaScript to render (SPAs, infinite-scroll listings, most modern storefronts). If a rendered page still comes back sparse, give it longer with wait_ms, or wait for a specific element with wait_for (a CSS selector) — that is more reliable than a fixed delay. Article-shaped pages have their navigation, cookie banners and footers stripped automatically; set main_content=false to keep the whole page. PDFs are extracted to text.

actions drives the page before reading it (implies js_render). Each is {action, selector, ...}: click, type (text), press (key), wait (ms), wait_for, scroll (times), scroll_to_bottom (max_rounds) for infinite scroll, and click_until_gone (max_clicks) for a 'load more' button. Use it for cookie gates, paginated listings and search forms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
actionsNo
wait_msNo
wait_forNo
js_renderNo
main_contentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and delivers: automatic stripping of navigation/cookie banners/footers for articles, PDF extraction to text, actions implying js_render, and detailed behavior of each action type. This is thorough and goes beyond what annotations would typically provide.

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?

Every sentence earns its place. The description is front-loaded with the core purpose, then systematically covers parameters and actions. It is dense but not bloated, with a clean two-paragraph structure that separates basic usage from advanced 'actions' behavior.

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 (6 parameters, an actions array, multiple rendering modes), the description is remarkably complete. It covers all parameters, explains the actions schema, and provides practical example use cases. The output schema exists, so return values don't need explanation.

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

Parameters5/5

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

The input schema has zero description coverage (only titles), so the tool description must compensate. It explains all parameters except the obvious 'url' — js_render, wait_ms, wait_for, main_content get clear usage context, and actions receives an entire paragraph with a complete list of action types and examples.

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 description opens with a specific verb 'Fetch' and clearly identifies the resource ('one web page') and the result ('clean markdown with metadata'). It distinguishes itself from sibling tools like fetch_pages (plural) and crawl_site by focusing on single-page retrieval with rendering options.

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?

The description provides extensive guidance on when to use each parameter: js_render for SPAs/infinite-scroll, wait_for over fixed delays, main_content to control stripping, and actions for cookie gates/paginated listings. It lacks explicit mention of when not to use this tool vs alternatives, so it's not a 5.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maccydee/cute-web-scraper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server