Skip to main content
Glama
zebbern

Webhook.site MCP Server

by zebbern
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

generate_canary_token

Create a canary URL, DNS name, or email that triggers an alert when accessed, to monitor unauthorized use of your files or systems.

Instructions

Make a canary URL, DNS name, or email that alerts when someone opens it.

    Use to mark your own files or systems. token_type='email' is a tripwire,
    not a sign-up inbox — use create_webhook + wait_for_email for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierNo
token_typeNourl
webhook_tokenYesWebhook UUID returned by create_webhook

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed11 schema fields changedv2.2.2
    • addedInput schema / properties / identifier / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / identifier / default
      Added value: +null
    • removedInput schema / properties / identifier / description
      Removed value: -"Custom identifier for the canary (e.g., 'confidential-doc', 'admin-panel')"
    • addedInput schema / properties / identifier / title
      Added value: +"Identifier"
    • removedInput schema / properties / identifier / type
      Removed value: -"string"
    • removedInput schema / properties / token_type / description
      Removed value: -"Type of canary token: 'url' (web link), 'dns' (DNS lookup), 'email' (email tracker)"
    • addedInput schema / properties / token_type / title
      Added value: +"Token Type"
    • changedInput schema / properties / webhook_token / description
      Previous value: -"The webhook token (UUID) from webhook.site"New value: +"Webhook UUID returned by create_webhook"
    • addedInput schema / properties / webhook_token / title
      Added value: +"Webhook Token"
    • addedInput schema / title
      Added value: +"generate_canary_tokenArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "generate_canary_tokenDictOutput",
+  "type": "object"
+}
  2. Addedv2.0.3
  3. Removedv2.0.0
  4. First observedv2.1.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It transparently states that the token 'alerts when someone opens it' and clarifies that email tokens are tripwires, not inboxes. However, it does not explicitly mention that alerts are sent via the required webhook_token, though this is implied by the parameter.

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 concise, consisting of two sentences that directly address purpose and usage caveats without unnecessary fluff. It is well-structured and easy to parse.

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?

Given the simplicity of the tool, the description covers its core purpose, usage, and a key behavioral note. It does not describe the return value, but that is not critical for this type of tool, and the output schema is not provided for evaluation. Overall, it is sufficiently complete for an agent to use correctly.

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 description explains token_type options by mentioning URL, DNS, and email, and the schema describes webhook_token. However, the identifier parameter is not explained at all, leaving some ambiguity about its purpose. Schema coverage is incomplete, so the description adds partial meaning but not full clarity.

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's function: 'Make a canary URL, DNS, or email that alerts when someone opens it.' It uses a specific verb and resource, and distinguishes it from sibling tools like create_webhook and wait_for_email.

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?

It provides explicit usage guidance: 'Use to mark your own files or systems.' It also warns against misuse for email ('not a sign-up inbox') and points to an alternative approach (create_webhook + wait_for_email), which clarifies when to use this tool versus others.

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/zebbern/webhook-mcp-server'

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