Skip to main content
Glama

scrapewise_delete_scraper_site

DestructiveIdempotent
        Permanently removes a Site (the URL inventory backing a fixed-URL-list scraper)
        and cascades to delete every Link attached to it. The scraper itself is NOT
        deleted — only the Site bound to it. Use to wipe a scraper's URL list when
        re-populating, or as part of a hermetic eval-environment teardown.

        Idempotent: deleting a site that's already gone returns 204 No Content rather
        than 404 (ADR-013 destructive idempotency — agent retries are safe).

        Args:
          - siteId (string, path param, required): the Site's MongoDB ObjectId. Get
            via `scrapewise_get_scraper_site` (which returns the site for a scraper).

        Returns:
          204 No Content. Empty body. Verify via a follow-up `scrapewise_get_scraper_site`
          call returning null.

        Examples:
          - Use when: "wipe the URL list of scraper {id}" → fetch site id via
            scrapewise_get_scraper_site, then call this op.
          - Use when: tearing down an eval-environment site before re-seeding fresh URLs.
          - Don't use when: you want to delete the scraper itself → use
            scrapewise_delete_scraper (or its preview/commit pair).
          - Don't use when: you want to remove specific URLs (not the whole site) → no
            per-link delete API today; re-PUT a smaller SiteDTO.

        Error Handling:
          - 204 on success OR on idempotent-retry of an already-deleted site.
          - 400 if siteId is not a valid ObjectId.
          - 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": {
      "siteId": "<siteId>"
    },
    "name": "scrapewise_delete_scraper_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesthe Site's MongoDB ObjectId. Get via `scrapewise_get_scraper_site` (which returns the site for a scraper).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / siteId / description
      Added value: +"the Site's MongoDB ObjectId. Get via `scrapewise_get_scraper_site` (which returns the site for a scraper)."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the cascade to every attached Link and what survives (the scraper), plus the 204-on-retry vs 404 semantics and the error taxonomy (400 invalid ObjectId, 401, 500). The one weakness is the claim of "204 No Content. Empty body," which sits awkwardly against the runtime hint that responses are dynamic JSON-as-text blobs and could set a wrong expectation about the return value.

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 scope and the critical 'scraper is not deleted' caveat, then organized into Returns / Examples / Error Handling sections where each sentence carries information. The Args block is partially redundant with a fully-covered schema and the Returns block is slightly over-confident about an empty body, keeping it just below full marks.

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 destructive one-parameter tool with no output schema, the definition covers blast radius, survival semantics, idempotency, verification path, and failure modes — everything needed to invoke safely. The residual gap is the return-value characterization, which conflicts with the dynamic-response hint and would leave an agent poorly prepared to parse the result.

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% and the single siteId parameter is fully documented in the schema with the same ObjectId/get_scraper_site pointer that appears in the Args section. The description restates rather than extends the schema, so the baseline 3 applies despite no value being added.

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 ("Permanently removes a Site") and immediately qualifies the resource ("the URL inventory backing a fixed-URL-list scraper"), then explicitly contrasts with the sibling deletion tool: "The scraper itself is NOT deleted — only the Site bound to it." An agent can distinguish this from scrapewise_delete_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?

Provides two positive conditions (wiping a URL list for re-population, eval-environment teardown) and two explicit exclusions with named alternatives — delete the scraper itself via scrapewise_delete_scraper, or shrink the URL list by re-PUTing a smaller SiteDTO. It also names the prerequisite lookup call (scrapewise_get_scraper_site) needed to obtain the siteId.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.