Skip to main content
Glama
js-cohn

Webhook.site MCP Server

by js-cohn

update_token

Modify Webhook.site token settings like CORS, alias, expiry, response status/content, request limits, and actions to tailor webhook behavior.

Instructions

Update settings of a Webhook.site token.

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)
token_idNoThe Webhook.site token UUID (or use WEBHOOK_SITE_TOKEN_ID env var)
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?

With no annotations, the description carries the full burden. It only states 'Update settings,' implying mutation, but does not disclose side effects, authentication needs, reversibility, or behavior on invalid input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no redundant words. It is front-loaded and not verbose, though it lacks detail.

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?

For a tool with 12 optional parameters and no annotations, the one-sentence description is insufficient. It does not explain update semantics, prerequisites, or how it fits with sibling operations, despite the output schema covering return values.

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 fully documents all 12 parameters. The description adds no parameter-specific information, meriting the baseline score of 3.

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 description uses the specific verb 'Update' and identifies the resource as 'settings of a Webhook.site token.' It distinguishes from siblings like get_token and delete_token, but does not enumerate specific settings, making it slightly less precise.

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?

No guidance is provided regarding when to use this tool versus alternatives. It does not mention prerequisites such as an existing token or explain how it differs from create_token/delete_token.

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