Skip to main content
Glama

scrapewise_delete_scraper

DestructiveIdempotent
        Permanently removes the scraper with the given id from the customer's account.
        By default the scraper's scraped data (in the associated group's MongoDB
        collection) is preserved; pass `withData=true` to also delete the scraped rows.

        Args:
          - id (string, path param, required): the scraper's MongoDB ObjectId.
          - withData (boolean, query param, optional, default false): if true, also
            deletes the scraped product data this scraper produced. Irreversible.

        Returns:
          204 No Content on success. The response body is empty.

        Examples:
          - Use when: "delete scraper {id}" → no extra args (preserves data)
          - Use when: "delete scraper {id} and its data" → withData=true
          - Don't use when: you want to pause but keep the scraper → set
            StartType.NONE on the group via scrapewise_update_scraper_group_start_type

        Error Handling:
          - 400 (CustomerError envelope) if no scraper with the given id exists for this customer.
          - 401 Unauthorized.
          - 409 RUN_STILL_ENDING: retry after 5 s.
          - 500 INTERNAL on unexpected 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_delete_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe scraper's MongoDB ObjectId.
withDataNoif true, also deletes the scraped product data this scraper produced. Irreversible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"the scraper's MongoDB ObjectId."
    • addedInput schema / properties / withData / description
      Added value: +"if true, also deletes the scraped product data this scraper produced. Irreversible."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description goes further: it states exactly which data is destroyed only when withData=true, that the operation is irreversible, the 204 empty-body response, and a full error table including 409 RUN_STILL_ENDING with a 5 s retry instruction. This is behavior an agent cannot get from the annotations alone.

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?

Well structured and front-loaded, with the destructive default clarified in the first two sentences. The Args and Returns blocks duplicate the schema and the runtime hint, adding some redundancy, but the Examples and Error Handling sections each earn their space.

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 destructive two-parameter tool with no output schema, everything an agent needs is present: return code and empty body, failure modes with retry guidance, and the interaction with the data-preservation default. The runtime hint about JSON-as-text further covers the missing output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds relational meaning: the default is non-destructive to scraped rows and withData opts into deletion of derived data. The Args block largely restates the schema, so it does not earn a 5.

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 with scope: 'Permanently removes the scraper with the given id from the customer's account.' It explicitly distinguishes its default behavior (data preserved) from the data-deleting variant, so an agent can tell it apart from scrapewise_delete_scraper_data 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 explicit 'Use when' examples mapped to argument choices and a 'Don't use when' case that names the alternative (pause via scrapewise_update_scraper_group_start_type with StartType.NONE). Routing between this tool and the pause path is unambiguous.

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.