Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_webhook_deliveries

Read-onlyIdempotent

List webhook delivery attempts newest first and filter by event type or event ID to trace retries and inspect each response for a subscription.

Instructions

Returns the delivery attempts of this subscription, newest first. Each entry records one attempt with the response it got, so a retried event appears once per attempt.

  • event_type: narrows the list to a single event type.

  • event_id: follows one event across every attempt made on it, without paging through the whole history.

BeeL API endpoint: GET /v1/accounts/{account_id}/webhooks/{webhook_id}/deliveries (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>"
    },
    "name": "beel_list_webhook_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. The response echoes it back as `pagination.current_page`.
limitNoHow many items to return per page. The response echoes it back as `pagination.items_per_page`.
event_idNoOnly deliveries of this event. Use it to follow every attempt on one event without paging through the whole history.
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.
event_typeNoOnly deliveries of this event type.
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.

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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real context: newest-first ordering, one record per attempt including the response, and that retried events appear multiple times. It says nothing about pagination behavior or result volume limits, which with annotations present keeps this at a solid 3 rather than higher.

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 summary sentence, then two tight bullets that each explain a filter's intent. Slight redundancy: the event_id bullet nearly duplicates the event_id property description, and the endpoint/reference footer is boilerplate. Still efficient overall.

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?

No output schema exists, and the description partially compensates by explaining the shape of each returned entry (one attempt plus the response it got). Combined with rich annotations and full schema coverage, an agent has enough to call it correctly; only pagination/result-size behavior is left implicit.

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%, so the schema already documents all six parameters thoroughly. The description's two bullets on event_type and event_id largely restate what the property descriptions already say, so it adds little meaning beyond the schema. 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?

States a specific verb and resource ('Returns the delivery attempts of this subscription') plus the ordering ('newest first') and the granularity ('one attempt with the response it got, so a retried event appears once per attempt'). An agent can distinguish this from beel_list_webhook_subscriptions and beel_retry_webhook_delivery 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?

Gives clear guidance on when to use each filter: event_type to narrow to a single type, event_id to follow one event across every attempt 'without paging through the whole history'. It lacks explicit when-not-to-use guidance or a named alternative (e.g., use beel_get_webhook_subscription for subscription config), so it falls short of a 5.

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