Scrapewise

scrapewise_get_scraper_load_site

Read-onlyIdempotent

        Fetches the given URL via the proxy infrastructure and returns the raw HTML as
        text/html. Use to inspect a page's structure when designing a scraper config or
        debugging selectors. Goes through the SSRF deny-list and the customer's HTTP
        rate limit. Optional cache (1 hour TTL on the cached-page service).

        Args:
          - url (string, query param, required): public HTTP(S) URL to fetch.
          - cookiesAcceptSelector (string, query param, optional): CSS selector for a
            cookie-banner accept button to click before extracting (rendered fetch only).
          - useCache (boolean, query param, optional): return cached HTML if available.

        Returns:
          The raw HTML response body as text/html. May be null if the upstream returned
          empty body.

        Examples:
          - Use when: "fetch the HTML at https://example.com so I can see what selectors
            exist" → url only
          - Use when: "fetch with cache to avoid hitting the site" → useCache=true
          - Don't use when: you want JSON-shaped data → use scrapewise_get_scraper_load_site_content

        Error Handling:
          - 400 SSRF_BLOCKED if URL is internal / link-local / cloud-metadata.
          - 429 if rate limit exceeded.
          - 502 if upstream unreachable.
          - 401 Unauthorized.

[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.

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": "scrapewise_get_scraper_load_site"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`useCache`	No
`cookiesAcceptSelector`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With readOnlyHint/idempotentHint already declared, the description still adds substantial behavior: SSRF deny-list filtering, customer HTTP rate limit, a 1-hour cache TTL, rendered-only applicability of the cookie selector, and full error taxonomy (400 SSRF_BLOCKED, 429, 502, 401). Minor tension: openWorldHint=false while the tool fetches arbitrary public URLs, though that annotation choice is debatable rather than contradicted outright.

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?

Front-loaded purpose, then Args/Returns/Examples/Errors sections that are easy to scan and free of filler. The Returns section partly restates what the runtime hint already conveys about dynamic responses, keeping it from a 5.

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?

For a 3-parameter fetch tool with no output schema, the definition covers inputs, output shape (raw HTML, may be null), caching, security filtering, rate limits, usage exclusions, and error codes. Nothing an agent needs to call it correctly is missing.

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 carries the full burden and does: url is required and must be public HTTP(S); cookiesAcceptSelector is optional, is a CSS selector, and only applies to rendered fetches; useCache returns cached HTML when available. This is meaning well beyond the bare type declarations.

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?

Opens with a specific verb+resource: fetches a given URL through proxy infrastructure and returns raw HTML as text/html. It also explicitly distinguishes itself from the sibling that returns JSON-shaped data (scrapewise_get_scraper_load_site_content), so an agent can route correctly without inspecting schemas.

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

Usage Guidelines5/5

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

Gives positive usage ('inspect a page's structure when designing a scraper config or debugging selectors'), a concrete negative case ('Don't use when: you want JSON-shaped data → use scrapewise_get_scraper_load_site_content'), and worked examples mapping intents to parameter choices.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scrapewise tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.