Scrapewise

scrapewise_get_scraper_site

Read-onlyIdempotent

        Returns the Site (URL inventory) attached to the given scraper, if any. Not
        every scraper uses a Site — only fixed-URL-list scrapers do (the
        "scrape-these-50-pages" pattern). Single-page scrapers and paginated
        category-listing scrapers don't have a Site and this endpoint returns null.
        Use to discover the URL list a scraper iterates over before viewing the
        scraped data, or as the first step in adding more URLs to a scraper's input
        inventory.

        Args:
          - id (string, path param, required): the SCRAPER's MongoDB ObjectId
            (NOT the site's id — the lookup is "site for this scraper").

        Returns:
          SiteDTO or null. SiteDTO carries name, link count summary, and ownership;
          the actual link inventory is paginated and lives at a separate endpoint.
          For the actual Link list, call scrapewise_get_scraper_site_links with the
          site's id from this response.

        Examples:
          - Use when: "what URLs does scraper {id} target?" → get site, then list links
          - Use when: planning to add URLs to a fixed-list scraper — get site, then
            PUT a new SiteDTO via scrapewise_create_scraper_site
          - Don't use when: scraper is a single-page or category-listing scraper →
            no Site; check scraper.config.sourceConfig.url on the scraper directly

        Error Handling:
          - 401 Unauthorized.
          - 500 INTERNAL.

[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_site"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety bar is low; the description still adds real behavior: the endpoint returns null for scrapers without a Site, SiteDTO carries name/link-count/ownership but the link inventory is paginated elsewhere, and it lists 401/500 error conditions. It also names the mutation sibling (scrapewise_create_scraper_site) for the write path.

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 key semantic and cleanly sectioned into Args/Returns/Examples/Error Handling, with zero filler prose. Slight redundancy in the Args block restating type and 'required' from the schema, and the two examples partially overlap, but nothing is confusing.

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?

There is no output schema, so the description carries the return burden — and it does: SiteDTO-or-null, its fields, and an explicit warning that the link list lives at a separate endpoint. Error handling and the runtime hint's dynamic-response caveat are both covered, leaving no obvious gap for a single-parameter read.

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 coverage is 0% — the lone 'id' property is completely undocumented in the schema. The description compensates fully by naming the type, the path-param location, the required flag, and above all clarifying that it is the scraper's MongoDB ObjectId and not the site's id.

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 — 'Returns the Site (URL inventory) attached to the given scraper' — and immediately scopes it ('only fixed-URL-list scrapers do'). It also disambiguates the id: the SCRAPER's ObjectId, not the site's. An agent can distinguish this from scrapewise_get_scraper_site_links and scrapewise_get_scraper without opening either schema.

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 explicit use cases ('discover the URL list a scraper iterates over', 'first step in adding more URLs') and an explicit 'Don't use when' exclusion pointing at the alternative (single-page/category-listing scrapers → read scraper.config.sourceConfig.url instead). The follow-up path to scrapewise_get_scraper_site_links is spelled out.

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.