Skip to main content
Glama
agentisend

agentisend

Register a webhook

create_webhook

Register a public HTTPS endpoint to receive subscribed event deliveries and obtain its signing secret once, enabling receivers to verify signatures and distinguish real deliveries.

Instructions

Purpose: register an endpoint to receive event deliveries. NOT for: retrieving a secret you lost. Store the signing secret when you get it. Returns: the endpoint and its signing secret, ONCE. Verifying that signature is the only way a receiver can tell a real delivery from anything else.

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": {
      "url": "<url>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAn https URL on a public host to deliver to.
eventsNoEvent types to subscribe to, spelled as in the event catalogue. Defaults to ["*"] — everything. A name that is not a real event type is refused.
svix_compatNoAlso sign each delivery with svix-id, svix-timestamp and svix-signature, so a verifier written for those headers keeps working.
payload_formatNonative is the default envelope. resend is {type, created_at, data} with data.email_id, data.to and data.bounce.type, subType and diagnosticCode.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
urlNo
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
eventsNo
secretNoThe signing secret, shown once.
disabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare the mutation, external-call, and non-idempotent hints, so the bar is lower. The description still adds the single most important behavior: the signing secret is returned ONCE and cannot be recovered, plus why signature verification matters. It doesn't mention that registration causes outbound deliveries to a third-party host or that urls must be validated, which are material for an openWorld tool.

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?

Labeled lines ('Purpose:', 'NOT for:', 'Returns:') front-load the essential facts with almost no filler. The closing sentence about signature verification is useful motivation but slightly drifts into receiver-side guidance rather than tool usage.

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?

An output schema exists, so return shape needn't be described, yet the description still flags the one-time secret exposure that a schema alone would not convey. For a five-parameter, externally-facing mutation tool, the remaining gap is minor: no statement about retry/idempotency behavior or outbound delivery implications.

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 every parameter, including the event enum, svix_compat, payload_format, and idempotency_key, is already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

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 description names a specific verb and resource: 'register an endpoint to receive event deliveries'. It also carves out a negative case ('NOT for: retrieving a secret you lost'), which helps separate it from list_webhooks/delete_webhook. It never names an actual sibling tool, so the differentiation is by use case rather than by explicit routing.

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 'Purpose' and 'NOT for' pairing clearly states when to call this tool and one case to avoid, and adds an actionable instruction ('Store the signing secret when you get it'). It doesn't point to an explicit alternative for secret recovery or mention how this relates to listing or deleting webhooks, so the guidance stops short of full routing.

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