Skip to main content
Glama

scrapewise_run_group_delivery_webhook_test

        Sends one signed PING to the group's webhook URL right now and answers what the receiver said, so you can
        check your endpoint and your signature check without waiting for a real event. The body is fixed:
        {"event":"PING","groupId":...,"deliveryId":...,"computedAt":...}, with the same headers as real events
        (X-Scrapewise-Event: PING, X-Scrapewise-Delivery, X-Scrapewise-Timestamp, X-Scrapewise-Signature). It is
        not queued and not retried. At most one test per minute per group.

        Args:
          - id (string, path, required): the group's id (you must own the group, and it must have a webhook).
          - 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:
          {delivered: true when the receiver answered 2xx, deliveryId, httpStatus (null when no answer), error
          (timeout, refused address, HTTP status text)}.

        Examples:
          - Use when: "test the webhook of group {id}" right after creating it.
          - Use when: the webhook shows FAILED or DEAD deliveries and the receiver was fixed.
          - Don't use when: you want real data -> wait for FILE_READY / DAY_* or get the delivery status.

        Error Handling:
          - 404 WEBHOOK_NOT_FOUND: the group has no webhook. 429 WEBHOOK_TEST_LIMIT: one test per minute.
          - 403 WEBHOOK_OWNER_ONLY; 503 WEBHOOK_UNAVAILABLE: webhooks are not available on this server right now.
          - 409 TAKE_OVER_ACTIVE; 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_run_group_delivery_webhook_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id (you must own the group, and it must have a webhook).
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, and it must have a webhook)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say non-readonly, open-world, non-idempotent, non-destructive; the description adds the fixed PING body, the exact header set, that delivery is neither queued nor retried, and the one-test-per-minute-per-group cap. These are operational traits an agent could not infer from the annotations.

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: outcome first, then args, returns, examples and error codes in labelled blocks. It is longer than strictly necessary because the Args block duplicates the schema descriptions, but each remaining section carries real information.

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?

With no output schema, the description fully specifies the returned object (delivered, deliveryId, httpStatus possibly null, error text) and enumerates the meaningful failure codes including the rate-limit and take-over conflicts. Enough for an agent to call it and interpret both success and failure.

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 description's Args block restates the schema text for id and customerRef almost verbatim, so little new meaning is added there. The only surplus is the implicit precondition that the group must exist with an owned webhook, which the schema also states, so the 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?

"Sends one signed PING to the group's webhook URL right now and answers what the receiver said" gives a precise verb, target and immediate outcome, and the definition separately distinguishes itself from waiting on real events and from get-delivery-status lookups. An agent can pick it out of the sibling set without opening the 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?

Explicit when-to-use cases (right after creating the webhook, after FAILED/DEAD deliveries once the receiver is fixed) plus an explicit "Don't use when" that names the alternative behaviours (real events / delivery status). Nothing is left implicit.

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.