Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

beel_test_webhook_subscription

Send a synthetic, signed test payload to a webhook subscription to verify endpoint reachability and delivery handling before relying on real events.

Instructions

Sends a synthetic payload to the subscription's URL immediately, outside the normal delivery queue. Use it to verify that your endpoint is reachable and handles deliveries correctly before you rely on real events.

The payload carries "test": true and synthetic data, and is signed like any other delivery, so it also verifies your signature check. It is not retried on failure and does not appear in the delivery history.

Repeating the call with the same Idempotency-Key returns the cached result without sending the test payload again.

Endpoint: POST /v1/accounts/{account_id}/webhooks/{webhook_id}/test

Input Schema

TableJSON 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.
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.
Behavior5/5

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

Beyond annotations (readOnlyHint false, etc.), the description discloses key behaviors: payload includes `test: true` and synthetic data, signature verification, no retries on failure, absence from delivery history, and idempotency caching behavior with the same Idempotency-Key. These are valuable, non-obvious traits an agent needs to know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is multi-paragraph but every sentence provides distinct value: purpose, payload characteristics, retry/history behavior, idempotency, and endpoint. It is well-structured and front-loads the purpose. No redundancy.

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 a test operation with no output schema, the description covers all necessary aspects: what it does, when to use, key side effects (no retry, no history, idempotency), and the endpoint. An agent has enough to decide when and how to call it correctly.

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 baseline is 3. The main description adds a bit about idempotency_key behavior ('Repeating the call with the same Idempotency-Key returns the cached result'), but the schema already details this. Overall, the description adds minimal extra beyond the schema, so a 3 is appropriate.

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?

The description explicitly states the action ('sends a synthetic payload'), the target (the subscription's URL), and the mode (immediately, outside the normal delivery queue). This clearly distinguishes it from sibling tools like create/delete/get webhook subscriptions and retry delivery, which have different purposes.

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?

The description gives a clear intended use: 'verify that your endpoint is reachable and handles deliveries correctly before you rely on real events.' It implies this is for testing only, but does not explicitly name alternative tools or conditions for not using it. The context makes it obvious, but explicit alternatives would push to 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/beel-es/beel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server