Skip to main content
Glama

Create a webhook

autoshort_create_webhook

Registers a public HTTPS URL to receive signed POST notifications when your videos complete or fail, replacing polling. Returns the HMAC signing secret once for signature verification.

Instructions

Register an https URL to receive a signed POST when any of the user's videos reaches COMPLETED (video.completed) or FAILED (video.failed), within about a minute — instead of polling. Returns the signing secret ONCE: verify X-Webhook-Signature = hex HMAC-SHA256(raw body, secret). The URL must be public (private/internal addresses are refused). Max 10 per account. Free.

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": "autoshort_create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// endpoint.
eventsNoDefault both video events.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, open-world, non-idempotent write; the description adds substantial context beyond that: the signing secret is returned ONCE, the verification formula (X-Webhook-Signature = hex HMAC-SHA256(raw body, secret)), a public-URL-only constraint with private/internal addresses refused, a max of 10 per account, ~1 minute delivery latency, and that it is free. These are exactly the operational facts an agent needs before calling.

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?

A single dense paragraph that front-loads the action and constraints; every clause (secret-once, HMAC formula, public URL, quota, latency) carries operational weight, with no filler.

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?

With no output schema, the description correctly explains the important return value (the one-time signing secret) and the verification procedure. It is nearly complete for a 3-parameter write tool, though the purpose of the `description` parameter and the wildcard event are left unstated.

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?

Schema coverage is 67%, and the description compensates by explaining that the url must be public https (private/internal refused) and that events default to both video events. It does not mention the optional `description` field or the "*" wildcard enum value, leaving a small gap.

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 a signed POST") and pins the exact triggering events (video.completed / video.failed). An agent can tell immediately this is webhook registration for completion/failure notifications, distinct from the delete_webhook sibling.

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 a clear condition for use — "instead of polling" — which tells the agent when this is the right choice over repeatedly calling a status tool. It does not explicitly name the alternative tool or state when not to use it (e.g. exceeding the 10-webhook cap), so it stops short of full routing guidance.

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