Skip to main content
Glama
js-cohn

Webhook.site MCP Server

by js-cohn

create_token

Create a new Webhook.site token to get a unique URL or email address for capturing and inspecting webhook requests, with options for custom responses, aliases, and expiration.

Instructions

Create a new Webhook.site token (URL / email address container).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corsNoIf true, adds CORS headers to responses
aliasNoSets a custom alias (regex: [a-zA-Z0-9-_]{3,32})
expiryNoSeconds until the token auto-expires (max/default: 604800, i.e. 1 week)
listenNoSeconds to listen for response from "Set Response" endpoint (max: 10)
actionsNoEnables or disables Custom Actions for the token
api_keyNoOptional Webhook.site API key (or use WEBHOOK_SITE_API_KEY env var)
timeoutNoSeconds to sleep before returning the response (max: 30)
clone_fromNoToken UUID to clone settings from
request_limitNoLimits request history stored (0 to 10000; default: 10000)
default_statusNoThe default HTTP response status returned to requests (200-599)
default_contentNoThe default response body content
default_content_typeNoThe default response Content-Type (e.g. 'text/html', 'application/json')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the core purpose and does not disclose side effects, authentication requirements, rate limits, or what happens on creation. For a mutation tool like create, this is a significant transparency gap.

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 a single, front-loaded sentence with no wasted words. It is efficient and directly communicates the core function, though it could be more informative.

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

Completeness2/5

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

Despite having 12 optional parameters and multiple sibling tools, the description is very thin. It does not explain typical use cases, the significance of a token, or how this tool relates to the siblings. The output schema may cover return values, but the description leaves the agent with insufficient context to understand the broader purpose.

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?

The input schema provides 100% coverage with descriptions for all 12 parameters, so the tool description adds no additional parameter semantics. The baseline of 3 applies because the schema already does the heavy lifting.

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 uses the specific verb 'Create' with the resource 'new Webhook.site token' and adds a clarifying parenthetical about it being a URL/email container. This clearly distinguishes it from sibling operations like update, delete, and get.

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites, exclusions, or scenarios where another tool would be more appropriate. The verb 'Create' implies its purpose, but the context of when to choose it is absent.

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

Install Server

Other Tools

Latest Blog Posts

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/js-cohn/Webhook.site-FastMCP'

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