Skip to main content
Glama

scrapewise_delete_scraper_data

DestructiveIdempotent
        Permanently removes all scraped rows from the customer's group MongoDB collection
        that were produced by the given scraperJobStatusId. The scraper config and the
        scraperJobStatus record itself are preserved — only the actual scraped product
        data is deleted. Use to clean up a bad run's data without removing the scraper.

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

        Returns:
          204 No Content.

        Examples:
          - Use when: "delete the data from the bad run {scraperJobStatusId}"
          - Don't use when: you want to delete the scraper config too → use
            scrapewise_delete_scraper with withData=true

        Error Handling:
          - 400 if scraperJobStatusId is not a valid ObjectId.
          - 400 (CustomerError envelope) if no run with that id exists for this customer.
          - 401 Unauthorized.
          - 409 if some rows of the run could not be deleted. The run is kept; call again.
          - 409 RUN_STILL_ENDING: retry after 5 s.
          - 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
scraperJobStatusIdYesthe run's MongoDB ObjectId. Get from scrapewise_get_scraper_load_history.

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. Get from scrapewise_get_scraper_load_history."
  2. Added

TDQS

A4.6/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 adds substantial context beyond them: exactly what survives the deletion, and the non-obvious 409 partial-failure semantics ('The run is kept; call again') plus the RUN_STILL_ENDING retry-after-5s case and ObjectId validation errors. This is the kind of failure-mode detail an agent cannot infer from structured fields.

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 front-loaded: the definitive statement of what is deleted and what is preserved comes first, followed by Args/Returns/Examples/Error Handling. The Args block largely duplicates the input schema, which is the only waste; otherwise every section carries actionable information.

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 single-parameter destructive tool with no output schema, the definition covers result ('204 No Content'), prerequisites (id source), alternatives, and the full error surface including partial-failure recovery. Nothing an agent needs in order to call or recover from this tool is missing.

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 schema description already says 'the run's MongoDB ObjectId. Get from scrapewise_get_scraper_load_history,' which the description restates nearly verbatim. The only added meaning is the 400-on-invalid-ObjectId consequence, so the baseline 3 for full schema coverage 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?

States a specific verb and resource ('Permanently removes all scraped rows ... produced by the given scraperJobStatusId') and immediately narrows scope by declaring what is preserved (config and scraperJobStatus record). This lets an agent 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?

Explicitly gives both directions: 'Use to clean up a bad run's data without removing the scraper' and 'Don't use when: you want to delete the scraper config too → use scrapewise_delete_scraper with withData=true.' It also routes the agent to scrapewise_get_scraper_load_history to obtain the required id.

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.