Skip to main content
Glama
KhaledDev

yet-another-web-scraper-mcp

by KhaledDev

get_page_content

Retrieve cleaned page HTML stripped of scripts and styles. Target specific elements via CSS selector and read long pages in chunks using an offset.

Instructions

Return the current page's HTML with // tags stripped out.

If selector is given (a CSS selector, e.g. ".recipe-card" or "#content"), only the matching element(s) are returned instead of the whole page, which avoids truncation on large pages. If the content is longer than max_length, it's truncated and the response tells you the offset to pass on the next call to read the following chunk.

If the page looks like a Cloudflare/Akamai/CAPTCHA challenge page rather than real content, a "bot-challenge page" warning is prepended (only on the first chunk, offset=0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNo
selectorNo
max_lengthNo

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 full burden and does so excellently. It discloses tag stripping, truncation behavior, offset continuation, and the bot-challenge warning, giving the agent a thorough understanding of side effects and edge cases.

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 adds value: the main purpose is stated first, followed by selector behavior, truncation mechanics, and an edge case warning. The structure is logical and efficient without redundancy.

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?

Despite no annotations and an output schema not shown, the description covers the tool's behavior comprehensively: input parameters, output format (offset for pagination, bot-challenge warning), and real-world usage considerations. This is fully adequate for the tool's complexity.

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 0% description coverage, but the description fully explains all three parameters: selector (CSS selector for element filtering), max_length (truncation limit), and offset (chunk read position). This compensates completely for the schema's silence.

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 clearly states the tool returns the current page's HTML with script/style/svg tags stripped, and optionally scoped by a CSS selector. This distinguishes it from sibling tools like get_page_links (links), get_table (tables), and get_json_ld (structured data).

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 clear context on when to use the selector (to avoid truncation on large pages) and how to handle pagination with offset. However, it does not explicitly mention when not to use this tool or name alternatives like get_page_links or get_table.

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/KhaledDev/yet-another-web-scraper-mcp'

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