Skip to main content
Glama

scrapewise_delete_group_delivery_webhook

DestructiveIdempotent
        Removes the group's webhook and its signing secret. Deliveries still waiting in the queue are not sent.
        This is also how the secret is changed: delete the webhook, then create it again (the new secret is
        answered once by that create call). Removing a webhook that does not exist is not an error.

        Args:
          - id (string, path, required): the group's id (you must own the group).
          - customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
            another customer's account (Take Over): that customer's customerUniqueRef. Leave it out otherwise.

        Returns:
          {deleted: true when a webhook was removed (false when the group had none), cancelledDeliveries: queued
          deliveries that will not be sent}.

        Examples:
          - Use when: "stop sending webhooks for group {id}".
          - Use when: rotating the webhook secret (delete, then create again).
          - Don't use when: you only want to pause it -> update the webhook with enabled: false (keeps the secret).

        Error Handling:
          - 403 WEBHOOK_OWNER_ONLY: the group is shared with you - only its owner can change the webhook.
          - 400 (CustomerError): no group with this id for this customer.
          - 409 TAKE_OVER_ACTIVE: send customerRef; 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_group_delivery_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id (you must own the group).
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the group's id (you must own the group)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructive=true and idempotent=true, so the safety profile is known, but the description adds substantial context: the signing secret is destroyed along with the webhook, queued deliveries are cancelled rather than sent, and deleting a non-existent webhook is a silent no-op. The Returns block and the 403 WEBHOOK_OWNER_ONLY ownership constraint are exactly the operational detail annotations cannot convey.

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 destructive outcome in sentence one, then structured into Args, Returns, Examples, and Error Handling. It is long, but the error codes and rotation workflow each carry real decision value. Minor duplication between the prose and the schema descriptions keeps it from a 5.

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 an idempotent destructive tool with no output schema, the definition supplies the return shape ({deleted, cancelledDeliveries}), ownership preconditions, and the main failure codes. The runtime hint about dynamic JSON responses is a platform caveat rather than a description gap. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3. The description earns above baseline by explaining that customerRef is tied to admin Take Over and the 409 TAKE_OVER_ACTIVE error, and by restating the ownership requirement on id. Some of this overlaps the schema text, which keeps it from a 5.

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+side effect: 'Removes the group's webhook and its signing secret.' It goes further to distinguish itself from the create path (secret rotation) and from the update path (pausing). An agent can identify this tool's role without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when' / 'Don't use when' examples, including the key alternative: pausing should use update with enabled:false instead. It also names the delete-then-create pattern for secret rotation. Slightly short of 5 only because the 'Use when' entries are examples rather than a full routing rule set.

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.