Skip to main content
Glama
Sign In
SkyNet Scraper

SkyNet Scraper

by zyetaone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

page

Open a URL in a real browser and extract its title, readable text, HTML, links, or a CSS-selected block, plus final URL after redirects. Use it to read articles, documentation, or search results.

Instructions

Open a web page in a real browser and return its title and readable text (optionally its HTML, links, or a CSS-selected block), plus the final URL after redirects. Use this to read an article, docs page or search result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL to open.
formatNotext (default), html, or links.
fallbackNoUsed only if the page serves a bot challenge: an alternative URL to fetch instead, typically the site's JSON/API endpoint.
selectorNoOptional CSS selector; only that block is returned.
max_charsNoTruncate the result (default 12000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: a real browser implies JS rendering, the final URL after redirects is returned, and the fallback parameter handles bot challenges. It omits failure modes, timeouts, login/paywall behavior, and any rate or concurrency limits, leaving meaningful gaps for a mutation-free but network-dependent tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and return values, then the use case. Dense but every clause earns its place; no filler or repetition.

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?

No annotations and no output schema, but the description compensates by describing the return shape, redirect handling, and bot-challenge fallback, which are the highest-risk unknowns. It remains incomplete on error behavior and rendered-content edge cases (e.g., lazy-loaded or auth-walled pages).

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all five parameters including enum values and the 200-200000 max_chars range. The description adds modest value by tying output modes (HTML, links, CSS-selected block) to their effects, but it does not explain defaults or the truncation behavior beyond what the schema states.

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?

States a specific verb and resource: open a web page in a real browser, return title, readable text, optional HTML/links/CSS block, and final URL after redirects. An agent can tell this is a page-fetch/read tool rather than a discovery tool, though the sibling 'search' is only implied via 'search result' rather than named.

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?

Gives clear usage context: read an article, docs page, or search result, which positions it as the follow-up to search. It does not explicitly state when not to use it or name the 'search' sibling as the alternative for discovery.

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