Skip to main content
Glama

scrapewise_delete_customer_schema

DestructiveIdempotent
        Permanently remove a JSON-Schema document owned by the authenticated customer.
        The path is rooted at `/customer/{id}` to make the customer-scope explicit;
        deleting a global schema requires admin tooling outside the MCP surface.
        **Destructive operation.** Once deleted, any AI_CONF scrapers that reference
        this schema will fail at runtime with a missing-schema error — they need to
        be reattached to a different schema (or deleted) BEFORE the schema is removed.
        PR-4b will split this op into `scrapewise_delete_customer_schema_preview` +
        `scrapewise_delete_customer_schema_commit` so an agent can show a "scrapers
        using this schema" preview before committing the deletion. For now, this is
        an immediate single-call delete.

        Args:
          - id (string, path param, required): the schema's MongoDB ObjectId. Get
            from scrapewise_list_customer_schema.

        Returns:
          204 No Content on success. The body is empty by design — the only meaningful
          response is the HTTP status. To verify deletion, call
          scrapewise_list_customer_schema and confirm the id is no longer present.

        Examples:
          - Use when: "delete my unused 'old-product-v1' schema" — fetch via list,
            copy id, call this op
          - Use when: cleaning up after migrating scrapers to a new schema version —
            make sure NO scrapers still reference the old id before deleting
          - Don't use when: you only want to stop using a schema temporarily →
            schemas have no soft-disable; consider versioning instead
          - Don't use when: PR-4b destructive split is available → prefer the
            _preview / _commit pair, which surfaces affected-scraper count first

        Error Handling:
          - 204 No Content on successful delete.
          - 401 Unauthorized if no Firebase JWT or API key.
          - 404 (CustomerError envelope) if no schema with that id exists or it's
            not owned by the authenticated customer.
          - 500 INTERNAL with `correlationId` if persistence fails mid-delete.

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

Input Schema

NameRequiredDescriptionDefault
idYesthe schema's MongoDB ObjectId. Get from scrapewise_list_customer_schema.

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. Get from scrapewise_list_customer_schema."
  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 the consequence annotations cannot convey: AI_CONF scrapers referencing the deleted schema fail at runtime and must be reattached first. It also documents the empty 204 body, the verification procedure via list, and the 401/404/500 error envelopes — real operational context beyond 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 destructive warning lands before the examples — and organized into Args/Returns/Examples/Error Handling blocks. It loses a point for the internal 'PR-4b will split this op' roadmap sentence, which is engineering-plan noise whose only actionable residue (prefer the preview/commit pair) is already stated in the Don't-use list.

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 one-parameter destructive delete with no output schema, everything an agent needs is present: where to get the id, the pre-delete dependency check, the 204 empty-body expectation with a verification path, and the error taxonomy. The runtime-hint caveat about a dynamic response blob is not relevant for a no-content delete.

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 description coverage is 100% for the single `id` parameter, and the schema text already says 'Get from scrapewise_list_customer_schema', so the description's Args note largely restates it. Baseline 3 applies; no additional format or lookup nuance is added.

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 remove a JSON-Schema document') plus the scope constraint ('owned by the authenticated customer', path rooted at /customer/{id}) and rules out the global variant. An agent can distinguish it from scrapewise_delete_customer_schema_preview and scrapewise_list_customer_schema 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' and 'Don't use when' pairs: cleanup after migration, fetching the id via list first, not for temporary disable (no soft-disable exists → version instead), and not when the _preview/_commit pair is available. Alternatives and the condition selecting them are both named.

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.