Skip to main content
Glama
zebbern

Webhook.site MCP Server

by zebbern
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

export_webhook_data

Export complete event payloads from captured HTTP, email, and DNS traffic. Use this to fetch full HTML bodies when list or wait tools truncate content.

Instructions

Full dump of captured HTTP/email/DNS events, including HTML and untruncated bodies.

Use this when list/wait tools omitted HTML or truncated a body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
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. Changed6 schema fields changedv2.2.2
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of requests to export (default: 100)"
    • addedInput schema / properties / limit / title
      Added value: +"Limit"
    • 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: +"export_webhook_dataArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "export_webhook_dataDictOutput",
+  "type": "object"
+}
  2. Addedv2.0.3
  3. Removedv2.0.0
  4. First observedv2.1.3

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full responsibility. While the tool appears to be a read-only data export (no side effects implied), the description does not explicitly state that it is non-destructive or mention any rate limits or permissions. It is adequate but could be more explicit.

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 brief and to the point, with no unnecessary words. It efficiently conveys the tool's function and when to use it.

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 description mentions the output includes 'HTML and untruncated bodies' which gives some context, but it does not explain the limit parameter or how pagination or data volume is handled. Since an output schema exists (as indicated), the return format need not be detailed, but the missing limit explanation leaves a slight gap in completeness.

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?

The webhook_token parameter is well described as 'Webhook UUID returned by create_webhook', but the limit parameter has no description in the schema nor in the tool description. With only one of two parameters documented, the schema coverage is low, and the description does not compensate.

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 purpose: 'Full dump of captured HTTP/email/DNS events, including HTML and untruncated bodies.' It also distinguishes itself from siblings with the explicit note 'Use this when list/wait tools omitted HTML or truncated a body.'

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?

The description provides explicit guidance on when to use this tool versus alternatives: 'Use this when list/wait tools omitted HTML or truncated a body.' This directly addresses the decision point among the sibling tools.

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