Webhook.site MCP Server

create_webhook_with_config

Create a webhook endpoint with custom status, response body, timeout, CORS, and alias to simulate an API for testing.

Instructions

Create a webhook that returns a custom status, body, timeout, CORS, or alias.

    Use when the user wants the endpoint to pretend to be an API (404, delay,
    JSON body) instead of a default 200. For a normal sign-up inbox, use
    create_webhook.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cors`	No
`alias`	No
`expiry`	No
`timeout`	No
`default_status`	No
`default_content`	No
`default_content_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed38 schema fields changedv2.2.2Aug 20, 2026
- addedInput schema / properties / alias / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / alias / default
```
Added value: +null
```
- removedInput schema / properties / alias / description
```
Removed value: -"Custom alias for the webhook URL (3-32 alphanumeric chars)"
```
- addedInput schema / properties / alias / title
```
Added value: +"Alias"
```
- removedInput schema / properties / alias / type
```
Removed value: -"string"
```
- addedInput schema / properties / cors / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / cors / default
```
Previous value: -falseNew value: +null
```
- removedInput schema / properties / cors / description
```
Removed value: -"Enable CORS headers for cross-domain requests"
```
- addedInput schema / properties / cors / title
```
Added value: +"Cors"
```
- removedInput schema / properties / cors / type
```
Removed value: -"boolean"
```
- addedInput schema / properties / default_content / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / default_content / default
```
Previous value: -""New value: +null
```
- removedInput schema / properties / default_content / description
```
Removed value: -"Default response content/body"
```
- addedInput schema / properties / default_content / title
```
Added value: +"Default Content"
```
- removedInput schema / properties / default_content / type
```
Removed value: -"string"
```
- addedInput schema / properties / default_content_type / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / default_content_type / default
```
Previous value: -"text/html"New value: +null
```
- removedInput schema / properties / default_content_type / description
```
Removed value: -"Default response Content-Type header"
```
- addedInput schema / properties / default_content_type / title
```
Added value: +"Default Content Type"
```
- removedInput schema / properties / default_content_type / type
```
Removed value: -"string"
```
- addedInput schema / properties / default_status / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / default_status / default
```
Previous value: -200New value: +null
```
- removedInput schema / properties / default_status / description
```
Removed value: -"Default HTTP response status code (200-599)"
```
- addedInput schema / properties / default_status / title
```
Added value: +"Default Status"
```
- removedInput schema / properties / default_status / type
```
Removed value: -"integer"
```
- addedInput schema / properties / expiry / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / expiry / default
```
Added value: +null
```
- removedInput schema / properties / expiry / description
```
Removed value: -"Seconds until webhook auto-expires (max 604800 = 1 week)"
```
- addedInput schema / properties / expiry / title
```
Added value: +"Expiry"
```
- removedInput schema / properties / expiry / type
```
Removed value: -"integer"
```
- addedInput schema / properties / timeout / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / timeout / default
```
Previous value: -0New value: +null
```
- removedInput schema / properties / timeout / description
```
Removed value: -"Seconds to wait before returning response (0-30)"
```
- addedInput schema / properties / timeout / title
```
Added value: +"Timeout"
```
- removedInput schema / properties / timeout / type
```
Removed value: -"integer"
```
- removedInput schema / required
```
Removed value: -[]
```
- addedInput schema / title
```
Added value: +"create_webhook_with_configArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "create_webhook_with_configDictOutput",
+  "type": "object"
+}
```
Addedv2.0.3Apr 30, 2026
Removedv2.0.0Apr 30, 2026
First observedv2.1.3Feb 12, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It conveys that the tool creates a webhook with customizable response behavior, but does not detail side effects, potential errors, or the impact of omitted parameters (e.g., defaults beyond the implied 200). It adds some context but not comprehensive transparency.

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?

The description is two concise sentences, both front-loaded and relevant. The first sentence states the core function, the second provides usage guidance with an alternative. No filler or redundancies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with seven optional parameters and an output schema (not shown). The description covers the primary use case but does not explain default behavior when no config is given, interactions between parameters, or how expiry works. It suffices for choosing the tool but not for fully predicting behavior without further schema info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all seven parameters. It only names five (status, body, timeout, CORS, alias) and does not elaborate on units, constraints, or the remaining params (expiry, default_content_type). The mapping is shallow and leaves significant gaps in understanding the parameters' meanings and valid values.

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?

The description clearly states the tool creates a webhook with custom status, body, timeout, CORS, or alias, and explicitly contrasts it with the simpler create_webhook for normal use cases. This distinguishes it from siblings and names the specific resources being configured.

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

Usage Guidelines5/5

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

Provides explicit guidance: use this tool when the endpoint should mimic an API (e.g., 404, delay, JSON body) rather than a default 200, and directs users to create_webhook for a standard sign-up inbox. This is strong when/when-not guidance with a named alternative.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zebbern/webhook-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server