Skip to main content
Glama

scrapewise_delete_scraper_group_preview

        First half of the destructive-op two-call protocol per ADR-012. Mints a 5-min
        `DestructiveOpToken` for the group-delete operation, returning it alongside a
        human-readable preview the agent surfaces to the user before committing.

        Changes none of your data; each call issues a new one-time confirm token.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - withData (boolean, query param, optional, default false): same semantics as
            `scrapewise_delete_scraper_group.withData` — included so the preview's args
            hash covers the destructive-args shape.

        Returns:
          `DestructivePreviewResponseDTO` with `token` (opaque UUID; supply to commit
          within 5 min), `opName`, `targetEntityId`, and `previewSummary` (entity type,
          cascade-row counts, warnings).

        Examples:
          - Use when: agent intends to delete a group and wants user confirmation first
            — render the summary, only proceed to `scrapewise_delete_scraper_group`
            with the token on approval.
          - Use when: `withData=true` — the preview's `warnings` array surfaces the
            irreversible-data-loss warning the user must see before committing.
          - Don't use when: read-only inspection → use `scrapewise_get_scraper_group_list`.
          - Don't use when: you've already previewed this op in the session → re-use
            the existing token within its 5-min TTL.

        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_delete_scraper_group_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
withDataNosame semantics as `scrapewise_delete_scraper_group.withData` — included so the preview's args hash covers the destructive-args shape.

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: +"same semantics as `scrapewise_delete_scraper_group.withData` — included so the preview's args hash covers the destructive-args shape."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the 5-minute token TTL, that each call issues a new one-time token (explaining the idempotentHint=false), that no user data is changed, the args-hash rationale, and the 401/500 error surface. This resolves the potentially confusing destructiveHint=false on a delete-path tool.

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 protocol purpose and the no-data-change guarantee, then organized into Args/Returns/Examples/Error Handling sections that are easy to scan. Slightly verbose — the withData rationale is repeated verbatim in both the description body and the schema — but nothing is filler.

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 compensates by enumerating the DestructivePreviewResponseDTO fields (token, opName, targetEntityId, previewSummary with cascade counts and warnings). Combined with the commit-handoff instruction and error cases, an agent has everything needed to call it and act on the result.

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 already 100%, so the baseline is 3; the description adds real value by labeling id as a path param and withData as a query param with default false, and by explaining why withData exists (so the preview's args hash matches the destructive call's arg shape) rather than just restating its type.

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 ('Mints a 5-min DestructiveOpToken for the group-delete operation') and explicitly frames itself as the first half of a two-call protocol, which cleanly separates it from the commit sibling scrapewise_delete_scraper_group.

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 when' conditions (intent to delete, wanting user confirmation; withData=true warning surfacing) and explicit 'Don't use when' conditions (read-only inspection → scrapewise_get_scraper_group_list; already previewed → reuse token within TTL). Alternatives are named by exact sibling name.

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.