Skip to main content
Glama

scrapewise_delete_scraper_group

DestructiveIdempotent
        Permanently removes the group AND every scraper inside it (cascade). By
        default the group's scraped MongoDB data is preserved; pass `withData=true`
        to also drop the data collection. Irreversible.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - withData (boolean, query param, optional, default false): if true, also
            drops the group's MongoDB data collection (all historical scraped rows lost).

        Returns:
          204 No Content.

        Examples:
          - Use when: "delete group {id} but keep the data" → no extra args
          - Use when: "delete group {id} AND its data" → withData=true
          - Don't use when: you want to delete one scraper inside the group → use
            scrapewise_delete_scraper

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 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_delete_scraper_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
withDataNoif true, also drops the group's MongoDB data collection (all historical scraped rows lost).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
    • addedInput schema / properties / withData / description
      Added value: +"if true, also drops the group's MongoDB data collection (all historical scraped rows lost)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further: cascade scope (all scrapers removed), the default preservation of MongoDB data, the precise consequence of withData (all historical scraped rows lost), irreversibility, and concrete error codes (400 for missing group, 401, 500). That is meaningful context beyond the structured hints.

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 irreversible cascade and data-preservation rule, then organized into Args/Returns/Examples/Error Handling. It is somewhat long and repeats parameter text already in the schema, but every section carries actionable information an agent would otherwise have to guess.

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, the definition covers what is destroyed, what is preserved by default, the exact flag that changes that, the success response (204), and the failure modes. The runtime hint about dynamic JSON-as-text responses is consistent with the stated 204 and leaves nothing an agent needs missing.

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% and the schema text largely mirrors the description's Args block, so little is newly added there. However, the Examples section maps natural-language intent onto the withData flag and clarifies the default-keeps-data behavior in operational terms, which the schema alone does not convey. A 4 reflects that added translation value beyond a high-coverage schema.

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 its scope spelled out: 'Permanently removes the group AND every scraper inside it (cascade).' It also implicitly separates itself from per-scraper deletion via the Don't-use line, so an agent can distinguish it 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 explicit when-to-use examples keyed to user intent ('delete group but keep the data' → no extra args; 'delete AND its data' → withData=true) plus an explicit 'Don't use when' pointing to scrapewise_delete_scraper. The alternative and the condition that selects it are named, not inferred.

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.