Scrapewise

scrapewise_get_scraper

Read-onlyIdempotent

        Fetches the full configuration of a single scraper owned by the authenticated
        customer: source URLs, item-field selectors, scraping mode (HTML / JSON-LD / API /
        Amazon), pagination strategy, post-processing rules, and metadata (lastRunState,
        createdAt, updatedAt). Use this AFTER you've identified the scraper id via
        `scrapewise_get_scraper_list` (or you already have an id from prior context).

        Args:
          - id (string, path param, required): the scraper's MongoDB ObjectId, e.g.
            "65a3b1c8d4e7f291a3b5c6d8". Get this from the `id` field of any
            `scrapewise_get_scraper_list` result.

        Returns:
          A full scraper configuration object (`ScraperDTO`): id, name, type,
          sourceConfig, itemsConfig, pagination, schema reference, postProcessRules,
          lastRunState, createdAt, updatedAt, and group association.

        Examples:
          - Use when: "show me the config of scraper {id}" → id from list
          - Use when: "what URL does scraper 'mototas' scrape?" → list first to get id,
              then call this and read sourceConfig.url
          - Don't use when: you only need the customer's full list of scrapers →
              use scrapewise_get_scraper_list (much smaller response)
          - Don't use when: you want to MODIFY the scraper → use scrapewise_create_scraper
              (which doubles as create-or-update by id)

        Error Handling:
          - 400 (CustomerError envelope) if no scraper with the given id exists for this
            customer (thrown as `CustomerError("Scraper with id: <id> not found")`; the
            ControllerExceptionHandler maps `CustomerError` → HTTP 400).
          - 401 Unauthorized if no valid Authorization header.
          - 500 INTERNAL on unexpected server error.

[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": {
      "id": "<id>"
    },
    "name": "scrapewise_get_scraper"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds real value beyond them: authorization requirements (401 without a valid Authorization header), the not-found semantics mapped to HTTP 400 via CustomerError, and a summary of the returned configuration shape. It does not cover rate limits or pagination behavior, but the runtime hint already addresses the dynamic response shape, so little is missing.

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 with the core verb and resource, then cleanly sectioned into Args/Returns/Examples/Error Handling. Slightly padded by near-duplicate "Use when" examples that restate the same list-then-fetch flow, but nothing is genuinely wasted.

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?

With no output schema, the description still enumerates the returned ScraperDTO fields, and the runtime hint covers the dynamic response shape. Prerequisites, error codes, and alternatives are all present, so an agent has everything needed to call this correctly.

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 carry the parameter, and it does: id is documented as a required path param, identified as a MongoDB ObjectId, given a concrete format example, and its provenance (the id field of a scrapewise_get_scraper_list result) is spelled out.

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?

States a specific verb and resource ("Fetches the full configuration of a single scraper") and enumerates exactly what is returned: source URLs, selectors, scraping mode, pagination, post-processing rules, and metadata. It explicitly distinguishes itself from scrapewise_get_scraper_list and scrapewise_create_scraper, so an agent can route without opening 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?

Provides explicit "Use when" and "Don't use when" clauses, with named alternatives for each exclusion: list for enumeration (smaller response) and create_scraper for modification (create-or-update). It also states the prerequisite (obtain the id from scrapewise_get_scraper_list or prior context).

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.