Skip to main content
Glama
Dasistaiden

whed-tools

by Dasistaiden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scrape_url

Fetch a webpage's HTML content, optionally render JavaScript for dynamic sites, and save the result as JSON for further extraction.

Instructions

Scrape a webpage and return its HTML content.

Args:
    url: The webpage URL to scrape
    javascript: Set to True for JavaScript-rendered sites (slower but handles dynamic content)
    wait_seconds: How long to wait for JavaScript to load (only used when javascript=True)
    save_path: Optional file path to save the result as JSON (e.g. "C:/Users/me/Desktop/result.json").
               If a directory is given, a timestamped filename is generated automatically.

Returns:
    Dictionary with html content, status code, and load time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
save_pathNo
javascriptNo
wait_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does reasonably well: it discloses the slowness tradeoff of javascript=True, the conditional coupling of wait_seconds, and the file-writing side effect of save_path including directory-to-timestamped-filename behavior. Gaps remain around failure modes, blocking/rate limits, and what happens on non-HTML responses, which keeps it below 5.

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?

The purpose is front-loaded in a single sentence, followed by tightly scoped Args and Returns sections. Every line adds information about a parameter's behavior; there is no filler or restatement.

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?

For a four-parameter tool with an output schema, the description covers the input contract thoroughly and need not explain return values. The only meaningful omission is guidance about alternatives among its many sibling tools, which is a routing concern rather than an invocation one.

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?

Schema description coverage is 0%, so the description must compensate, and it does: each of the four parameters is documented with meaning beyond its name, including conditional semantics ('only used when javascript=True') and non-obvious save_path behavior when a directory is passed. This is exactly what a low-coverage schema requires.

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

Purpose4/5

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

The description opens with a specific verb+resource: 'Scrape a webpage and return its HTML content.' That is unambiguous about the action and the payload. It does not, however, differentiate from siblings like batch_scrape, crawl_website, or extract_data, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the javascript flag ('Set to True for JavaScript-rendered sites'), which is useful conditional guidance. There is no explicit statement of when to prefer this tool over batch_scrape or crawl_website, no exclusions, and no prerequisites. Adequate but not routing guidance.

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