Skip to main content
Glama

configure_webhook

Destructive

Manage webhook subscriptions for email events like replies, bounces, complaints, and unsubscribes. Create requires a public HTTPS URL and event types; update or delete by ID. Delivery signed with HMAC-SHA256.

Instructions

Manage an outbound webhook subscription. action = create (needs url + eventTypes: reply|bounce|soft_bounce|complaint; optional secret/active) | update (needs id + one changed field; active:true re-enables an auto-disabled one, active:false pauses; secret rotates) | delete (needs id). create/rotate return the HMAC signing secret ONCE. URLs must be https to a public host (private/metadata IPs rejected). Deliveries are signed X-Coldrig-Signature: sha256=HMAC-SHA256(secret, raw body).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRequired for update/delete.
urlNoRequired for create. HTTPS endpoint; private/link-local/metadata IPs are rejected.
noteNoIgnored placeholder for symmetry; webhooks record no provenance note.
actionYes
activeNoOptional. On update, active:true re-enables an auto-disabled subscription; active:false pauses delivery.
secretNoOptional signing secret (>=16 chars). Omit on create to have one generated; pass on update to rotate.
eventTypesNoRequired for create: which events to push (reply | bounce | soft_bounce | complaint).
Behavior5/5

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

The description discloses key behaviors beyond the destructiveHint annotation: secret returned only once, HTTPS requirement, rejection of private IPs, HMAC signing, and re-enable/pause semantics for active flag. This is comprehensive.

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 description is a single, dense paragraph that front-loads the purpose and then details actions. While effective, it could be broken into bullet points for easier scanning, but no unnecessary sentences are present.

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?

Given the tool's complexity (3 actions, 7 parameters, no output schema), the description covers all actions, parameter dependencies, constraints (URLs, event types), and return behavior (secret once). It is fully informative.

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?

Despite high schema coverage (86%), the description adds context like 'secret rotates', 'active:true re-enables an auto-disabled one', and 'ignored placeholder' for note, enriching the schema definitions.

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 clearly states 'Manage an outbound webhook subscription' and enumerates the three actions (create, update, delete), making the tool's purpose specific and distinct from sibling tools like get_webhooks.

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 provides detailed usage patterns for each action, including required and optional parameters. However, it does not explicitly contrast with sibling tools or state when not to use this tool, leaving a minor gap.

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/YS-projectcalc/agent-cold-email'

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