Skip to main content
Glama

Create a webhook

create_webhook

Register an https URL to receive events as Standard Webhooks: a POST with webhook-id, webhook-timestamp and webhook-signature (v1, HMAC-SHA256 of id.timestamp.body with the secret returned here, once). scope mine sends your own polls' events, public every public poll's; poll_id narrows it to one poll. Only events after it is made are sent. Answer 2xx to acknowledge; failures are retried for about three days, and 410 stops deliveries. (POST /api/v1/webhooks)

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
urlYesYour receiver's https URL.
scopeNomine: your own polls. public: every public poll.mine
eventsNoWhich event types to send. Default: all.
poll_idNoOnly this poll's events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past annotations: the secret is returned once and used for HMAC-SHA256 over id.timestamp.body, only future events are delivered, 2xx acknowledges, failures retry ~3 days, and 410 terminates delivery. This is the operational knowledge an agent needs and cannot get from structured fields.

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-loads the action and the wire contract, then moves to scoping and delivery semantics. It is dense and slightly run-on in the middle, but every clause carries useful information and nothing is padding.

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 four-parameter mutation with no output schema, the description covers the registration action, the signing contract, the scoping model, and the full delivery lifecycle including retry and termination. Nothing an agent needs in order to call it correctly 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 coverage is 100% and the schema already spells out url, scope, events defaults, and poll_id. The description restates scope and poll_id semantics rather than adding new detail, so 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 ('Register an https URL to receive events') and immediately qualifies it with the payload contract (Standard Webhooks POST with id/timestamp/signature). This is unmistakably distinct from list_webhooks and delete_webhook.

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?

Explains the two scoping modes and how poll_id narrows them, which tells the agent how to configure the call for a given intent. It does not explicitly contrast against sibling tools or state prerequisites, so it falls short of a full when/when-not rubric.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.