Skip to main content
Glama

scrapewise_delete_api_key

DestructiveIdempotent
        Permanently removes the key with the given id for the authenticated customer.
        The key cannot be used after this call returns (any in-flight request using
        it will succeed, but new requests get 401). Revocation is a hard delete today;
        an `active=false` soft-revoke is on the M1 follow-up list. Idempotent —
        deleting a non-existent or wrong-customer id is a silent no-op.

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

        Returns:
          200 OK with empty body. Idempotent (succeeds even if id doesn't exist).

        Examples:
          - Use when: "revoke the 'ci-deploy' key" → list first to find id, then delete
          - Don't use when: you want to ROTATE a key → revoke + create_api_key
            (no rotate-in-place API)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe key's MongoDB ObjectId. Get from scrapewise_list_api_keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the key's MongoDB ObjectId. Get from scrapewise_list_api_keys."
  2. Added

TDQS

A4.5/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 genuinely new behavior: in-flight requests succeed while new ones get 401, revocation is a hard delete with a planned soft-revoke, and deleting a wrong-customer or non-existent id is a silent no-op. It also enumerates error codes (401, 500).

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 action and its effect, then well-partitioned into Args/Returns/Examples/Error Handling. Minor redundancy: idempotency-as-no-op is stated twice (body text and Returns), and idempotentHint is already in annotations.

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?

For a single-param destructive tool with no output schema, the description covers prerequisites, side effects, and errors thoroughly. The only soft spot is that it promises an 'empty body' while the runtime hint warns the response is a dynamic JSON-as-text blob, so an agent may be mildly misled about the return payload.

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 param's description already says it is the MongoDB ObjectId retrievable from scrapewise_list_api_keys, so the description largely restates the schema. Baseline 3 applies; it adds no format or validation detail beyond the schema.

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?

Opens with a specific verb+resource+scope: "Permanently removes the key with the given id for the authenticated customer." It is clearly distinguishable from scrapewise_list_api_keys and scrapewise_create_api_key, which it names as the source of the id and as the counterpart for rotation.

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' examples, states the prerequisite workflow (list first to find the id), and names the concrete alternative for rotation (revoke + create_api_key, since no rotate-in-place API exists).

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.