Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_retry_webhook_delivery

DestructiveIdempotent

Re-sends the original payload of a webhook delivery immediately to recover failed or missed webhook events, recording the retry as a new history entry while preserving the original.

Instructions

Re-sends the original payload of a delivery immediately.

  • Payload: the one captured when the event happened, not a fresh snapshot, so changes made to the entity since then are not reflected.

  • History: the outcome is recorded as a new entry and the original entry is kept as it was. attempt_number continues the same sequence, so it can exceed the number of automatic attempts.

BeeL API endpoint: POST /v1/accounts/{account_id}/webhooks/{webhook_id}/deliveries/{delivery_id}/retry (reference: https://docs.beel.es)

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": {
      "account_id": "<account_id>",
      "webhook_id": "<webhook_id>",
      "delivery_id": "<delivery_id>"
    },
    "name": "beel_retry_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesYour own account, or an account you provisioned. It — not the credential, and not the `BeeL-Active-Company` header — decides which account the operation acts on. An account you do not reach answers `403`, and so does an account that does not exist, so the existence of somebody else's account is never disclosed.
webhook_idYesSubscription of the account in the path. A subscription of another account answers `404`, the same as one that does not exist: under the account resolved from `{account_id}` it simply is not there.
delivery_idYesDelivery attempt of that subscription to replay.
idempotency_keyNoOptional idempotency key for this operation. Omit it and one is derived from the request itself, which makes a blind retry safe but also collapses a SECOND, deliberately identical operation into the first for 24 hours. Set it — to an order id, or anything unique per intended operation — whenever you mean to create something that may look identical to what you just created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A3.9/5.0
Behavior5/5

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

Well past the bar set by the annotations, the description discloses that the replayed payload is the one captured at event time rather than a fresh snapshot, that the outcome appends a new history entry while the original entry is preserved, and that attempt_number continues the existing sequence and may exceed the automatic attempt count. Those are non-obvious side-effect details an agent could not infer from destructiveHint/idempotentHint alone.

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?

The lead sentence is front-loaded and the two bullets each earn their place by conveying payload staleness and history semantics. The trailing API endpoint line plus docs URL is mildly redundant given the tool name and annotations, but it is short and does not bury the important content.

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 mutating, open-world tool with no output schema, the description covers the essential behavioral facts: what gets sent, what gets recorded, and how the attempt counter behaves. It stops short of describing the response body or any permission requirements, but nothing critical for a correct invocation 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 description coverage is 100%, including detailed account_id, webhook_id, delivery_id and idempotency_key text, so the schema carries parameter meaning. The description adds nothing about the three path identifiers and does not discuss the idempotency_key collapse window, leaving it entirely to the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb plus resource and scope: re-sending the original payload of an existing delivery. That is clearly distinct from creation-oriented siblings like beel_create_webhook_subscription, but the description never names a sibling or states its boundary against beel_test_webhook_subscription or beel_list_webhook_deliveries explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: you would call this to replay a delivery that failed or needs re-sending. There is no explicit when-to-use/when-not statement, no guidance on checking beel_list_webhook_deliveries first, and no mention of the difference versus beel_test_webhook_subscription, which is the closest alternative for sending webhook traffic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools