Skip to main content
Glama

scrapewise_delete_customer_schema_preview

        First half of the destructive-op two-call protocol per ADR-012. Mints a 5-min
        `DestructiveOpToken` for the customer-schema-delete operation. The agent surfaces
        the preview (including any warning about AI_CONF scrapers referencing this
        schema) before committing.

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

        Args:
          - id (string, path param, required): the schema'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 schema and wants the user to confirm —
            preview, render the summary, then commit on approval.
          - Use when: cleaning up after migrating scrapers to a new schema version —
            the preview is the audit point before the irreversible delete.
          - Don't use when: you only want to read the schema → use
            `scrapewise_list_customer_schema`.
          - 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_customer_schema_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe schema's MongoDB ObjectId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the schema'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?

Goes well beyond the annotations: states that no data is changed, that each call mints a new one-time token with a 5-minute TTL, that the preview surfaces warnings about AI_CONF scrapers referencing the schema, and lists 401/500 errors. This is consistent with destructiveHint=false since the preview itself is non-destructive while the paired commit is not.

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 with the protocol role, followed by Args/Returns/Examples/Errors. Slightly redundant: the 5-minute token lifetime is stated twice and the two 'Use when' bullets overlap, costing some tightness.

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?

No output schema exists, but the Returns section names the DTO and its fields (`token`, `opName`, `targetEntityId`, `previewSummary`), and the TTL, error cases, and commit handoff are all covered. Nothing an agent needs to call and complete the flow 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 single `id` parameter is already documented as the schema's MongoDB ObjectId. The description only restates 'path param, required' and adds no new format or lookup guidance, so the schema does the work here.

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 verb and resource: it mints a `DestructiveOpToken` for the customer-schema-delete operation, explicitly framed as the first half of a two-call protocol. An agent can distinguish it from `scrapewise_delete_customer_schema` (the committing sibling) 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 'Use when' cases (user confirmation flow, audit point before irreversible delete) and 'Don't use when' exclusions that name the correct alternative (`scrapewise_list_customer_schema`) and the token-reuse case. Nothing 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.