Skip to main content
Glama

scrapewise_delete_enrichment

DestructiveIdempotent
        Removes a group's enriched sibling dataset AND its saved join recipe, so the group is no
        longer enriched and will not auto-re-merge on future runs. Use to undo a wrong enrichment
        before making a new one (to redo, just enrich again — it overwrites). Idempotent: clearing
        when nothing is enriched returns 204. Rejected with 409 if a merge is currently running.

        Args:
          - id (string, path param, required): the original group's MongoDB ObjectId.

        Returns:
          204 No Content.

        Examples:
          - Use when: "clear / undo the enrichment on group {id}"
          - Use when: "remove the enriched data so I can redo it" → same op
          - Don't use when: you only want to delete one source run's data → use
            scrapewise_delete_scraper_data

        Error Handling:
          - 409 if an enrichment merge is currently running for the group.
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 401 Unauthorized.

[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_enrichment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe original group's MongoDB ObjectId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the original group's MongoDB ObjectId."
  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 destructive=true and idempotent=true, but the description goes well beyond them: it discloses that the join recipe is deleted alongside the dataset, that an empty clear returns 204, that a concurrent merge yields 409, and that a missing group yields 400 in a CustomerError envelope. These are exactly the edge behaviors an agent needs before firing a destructive call.

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: the core semantics land in the first sentence, with Args/Returns/Examples/Error Handling sections following. Slightly padded — the two 'Use when' examples say essentially the same thing, and the Args line duplicates the schema — but no sentence is misleading or wasted enough to hurt readability.

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?

Although no output schema exists, the Returns section states 204 No Content, and the runtime hint about dynamic JSON-as-text responses is present. Combined with the error catalog and idempotency note, an agent has everything needed to call this destructive tool safely and interpret the outcome.

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?

With a single required path parameter and 100% schema coverage, the schema already carries the meaning. The description's Args block restates 'the original group's MongoDB ObjectId' verbatim from the schema, adding no interpretation such as format examples or how to obtain the id. 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?

States a specific verb and resource — removes a group's enriched sibling dataset AND its saved join recipe — and explains the resulting state (group no longer enriched, no auto-re-merge). It also distinguishes itself from the closest sibling by naming scrapewise_delete_scraper_data as the alternative for deleting a single source run's data.

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 when-to-use cases ('clear/undo the enrichment', 'remove the enriched data so I can redo it'), an explicit don't-use case with the correct alternative tool, and even tells the agent that re-enriching overwrites rather than requiring a delete first. Nothing material is left to inference.

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.