Gumlet MCP

create_webhook

Creates a new webhook listener. Gumlet POSTs JSON to url for each matching event and sends secret_token in the x-gumlet-token header. Payload schemas are documented in the webhooks section.

Input Schema

Name	Required	Description
`url`	No	URL from the application you want to send data to.
`sources`	No	List of video collection identifiers for which webhooks are needed to be invoked.
`triggers`	No	Events that invoke this webhook. `status` subscribes to every video asset status event. `live-video-status` subscribes to every live video status event. Any other value subscribes to that event only.
`secret_token`	No	Secret sent back in the `x-gumlet-token` header of each webhook POST so you can confirm the request came from Gumlet.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

changedInput schema / properties / secret_token / description

Previous value: -"Authentication token to ensure legitimacy of Gumlet Webhook request on your application."New value: +"Secret sent back in the `x-gumlet-token` header of each webhook POST so you can confirm the request came from Gumlet."

changedInput schema / properties / triggers / description

Previous value: -"Triggers for the invocation of webhookos, supported option is `status`."New value: +"Events that invoke this webhook. `status` subscribes to every video asset status event. `live-video-status` subscribes to every live video status event. Any other value subscribes to that event only."

addedInput schema / properties / triggers / items / enum

Added value: +[
+  "status",
+  "live-video-status",
+  "video.status.created",
+  "video.status.downloaded",
+  "video.status.optimized",
+  "video.status.ready",
+  "video.status.errored",
+  "video.status.deleted",
+  "video.status.repackaged",
+  "video.status.stream_ready",
+  "live.video.status.created",
+  "live.video.status.ready",
+  "live.video.status.preparing",
+  "live.video.status.connected",
+  "live.video.status.active",
+  "live.video.status.complete",
+  "live.video.status.disconnected",
+  "event.embed.viewed",
+  "event.embed.cta_clicked",
+  "event.video.updated",
+  "event.video.uploaded",
+  "event.playlist.created",
+  "event.playlist.asset",
+  "event.playlist.deleted",
+  "event.video.analytics",
+  "event.image.analytics",
+  "event.embed.form_submitted",
+  "event.comment.all",
+  "event.channel.member_joined"
+]

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent, open-world), so the bar is lower. The description still adds real behavioral context beyond them: Gumlet delivers JSON POSTs per matching event and transmits secret_token in the x-gumlet-token header, which tells the agent how the created resource actually behaves at runtime.

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?

Three tight sentences: purpose first, then runtime behavior, then a pointer to the payload documentation. No filler and nothing important buried.

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 values need no explanation, and all four parameters are fully described in the schema. The description covers the creation semantics and delivery mechanism; the only gap is that it never notes that all parameters are optional or what a minimally valid webhook requires.

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 schema already carries the parameter detail. The description reinforces url and secret_token but repeats the schema's own wording for secret_token and says nothing at all about sources or triggers, so it adds little beyond the structured fields.

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 opening sentence gives a specific verb and resource ('Creates a new webhook listener'), which cleanly separates it from update_webhook, delete_webhook, and list_webhooks. It never names a sibling or an exclusion, so it stays at a clear-but-undifferentiated 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites (e.g. plan limits, permissions), and no mention of alternatives such as update_webhook for modifying an existing registration. Usage is only weakly implied by 'Creates a new webhook listener.'

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

All Gumlet MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?