Skip to main content
Glama

scrapewise_delete_scraper_data_preview

        First half of the destructive-op two-call protocol per ADR-012. Mints a 5-min
        `DestructiveOpToken` for the run-data-delete operation. The agent surfaces the
        preview before committing.

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

        Args:
          - scraperJobStatusId (string, query param, required): the run's MongoDB ObjectId.

        Returns:
          `DestructivePreviewResponseDTO` with `token` (opaque UUID; supply to commit
          within 5 min), `opName`, `targetEntityId`, and `previewSummary`.

        Examples:
          - Use when: agent intends to delete a bad run's data and wants the user to
            confirm — preview, render the summary, then commit on approval.
          - Don't use when: you want to delete the scraper config too → use
            `scrapewise_delete_scraper_preview` with `withData=true`.
          - Don't use when: read-only inspection → use `scrapewise_get_scraper_load_history`.

        Error Handling:
          - 400 if scraperJobStatusId 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": {
      "scraperJobStatusId": "<scraperJobStatusId>"
    },
    "name": "scrapewise_delete_scraper_data_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
scraperJobStatusIdYesthe run's MongoDB ObjectId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scraperJobStatusId / description
      Added value: +"the run's MongoDB ObjectId."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only flag readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the description adds real value: it states no data is changed, each call mints a fresh one-time token, the token expires in 5 minutes, and lists 400/401/500 failure modes. The one inconsistency is that it promises a DestructivePreviewResponseDTO with specific fields while the runtime hint says the response shape is dynamic and no outputSchema exists — that undercuts the Returns section, though it is a conflict with the runtime hint rather than with the annotations.

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 role and the non-destructive guarantee, then structured Args/Returns/Examples/Error blocks that are easy to scan. Slightly verbose for a one-parameter tool, and the Returns block asserts field names the runtime hint says cannot be relied upon.

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?

Because there is no output schema, the description carries the burden of describing returns and does so, including the token handoff to the commit call — which is the critical thing an agent needs. It loses a point because the enumerated response fields conflict with the stated dynamic-response behavior, leaving the agent unsure what the preview actually contains to surface to the user.

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?

Single required parameter with 100% schema description coverage, so the schema already carries the meaning. The definition restates it as 'the run's MongoDB ObjectId' and adds nothing about format, sourcing, or how to obtain the ID, so baseline 3 applies.

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?

Names a specific operation (minting a 5-minute DestructiveOpToken) for a specific resource (a run's data), and frames it precisely as the first half of a two-call protocol. It distinguishes itself from scrapewise_delete_scraper_preview and the commit step without the agent needing to open any 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?

Explicit 'Use when' with the full intended flow (preview, render summary, commit on approval) plus two 'Don't use when' exclusions that name the correct alternatives — the withData=true scraper-config delete and the read-only load-history tool. The selection conditions are spelled out rather than implied.

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.