Skip to main content
Glama
kroqdotdev

webhooks-cc

by kroqdotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_endpoint

Create a temporary webhook capture endpoint in the agent sandbox to inspect incoming requests. Register the sandbox on first call; endpoints capture up to 25 requests each.

Instructions

Create a temporary webhook capture endpoint in the agent sandbox (no account needed): up to 3 endpoints at a time, 25 captured requests each and 100 in all, deleted 24 hours after the sandbox was created. The first call registers the sandbox, which takes a few seconds of proof of work. Mock responses, notifications and signature verification need an account: see connect_account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name for the endpoint
ephemeralNoCreate a temporary endpoint that auto-expires
expiresInNoAuto-expire after this duration, for example "12h"
mockResponseNoOptional mock response to return when the endpoint receives a request
responseRulesNoConditional response rules. Each rule has conditions and a response. First matching rule wins.
signingHeaderNoCustom signature header name. Only used with generic-hmac provider.
signingSecretNoSigning secret (encrypted server-side, never returned). Required when signingProvider is set.
notificationUrlNoURL to POST a JSON summary to after each captured request (e.g. Slack/Discord webhook)
signingProviderNoSigning provider for automatic signature verification (e.g. stripe, github, shopify)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and delivers: quota limits (3 endpoints, 25 requests each, 100 total), lifecycle (deleted 24h after sandbox creation), latency (first call does proof of work, a few seconds), and account prerequisites. These are exactly the non-obvious traits 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?

Two sentences, both dense with information and no filler. Purpose is front-loaded, followed by limits, lifecycle, latency, and the account routing clause, in that priority order.

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?

Covers lifecycle, quotas, latency, and prerequisites for a complex 9-parameter nested-schema tool, which is strong. The one notable gap is that no output schema exists and the description never says what is returned (e.g. the capture URL), which an agent needs to actually use the endpoint.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by tying mock responses, notifications, and signature verification to an account requirement, which constrains mockResponse, notificationUrl, signingProvider, and signingSecret. It does not enumerate individual params, but the added constraint is real.

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 ("Create a temporary webhook capture endpoint in the agent sandbox") and scopes it precisely as an account-free sandbox operation, which separates it from connect_account and the read/manage siblings. An agent can tell what this tool produces without opening the schema.

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 clear when-to-use context (no account needed, temporary sandbox capture) and routes account-dependent features (mock responses, notifications, signature verification) explicitly to connect_account. It stops short of contrasting against the other siblings like list_endpoints or wait_for_request, but the primary alternative is named.

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

Deploy Server

Other Tools