Skip to main content
Glama
zebbern

Webhook.site MCP Server

by zebbern
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

extract_links_from_request

Extract verification, login, password-reset, and magic links from captured webhook requests or emails. Use after waiting for email or inspecting requests to retrieve the needed URL or OTP.

Instructions

Pull confirm, reset, magic-link, and other URLs from a captured email or HTTP body.

    Use after wait_for_email or get_webhook_requests when the user needs
    the verification / login / password-reset link or OTP. Defaults to the
    latest event. wait_for_email already extracts links and codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idNo
filter_domainNo
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. Changed14 schema fields changedv2.2.2
    • addedInput schema / properties / filter_domain / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / filter_domain / default
      Added value: +null
    • removedInput schema / properties / filter_domain / description
      Removed value: -"Only return links matching this domain"
    • addedInput schema / properties / filter_domain / title
      Added value: +"Filter Domain"
    • removedInput schema / properties / filter_domain / type
      Removed value: -"string"
    • addedInput schema / properties / request_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / request_id / default
      Added value: +null
    • removedInput schema / properties / request_id / description
      Removed value: -"Specific request UUID to analyze (optional, defaults to latest)"
    • addedInput schema / properties / request_id / title
      Added value: +"Request Id"
    • removedInput schema / properties / request_id / type
      Removed value: -"string"
    • 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: +"extract_links_from_requestArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "extract_links_from_requestDictOutput",
+  "type": "object"
+}
  2. Addedv2.0.3
  3. Removedv2.0.0
  4. First observedv2.1.3

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must bear the burden of explaining behavior. It mentions defaulting to the latest event and the relationship with wait_for_email, but it does not clarify the roles of request_id and filter_domain, nor does it address potential side effects or error conditions. Thus, behavior is only partially transparent.

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 relatively brief—four sentences—and conveys essential usage information without excessive verbosity. However, the sentence about wait_for_email already extracting links could be seen as slightly redundant, but it does help distinguish the tool, so it is not wasted.

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 provides enough context for when to use the tool and mentions the default behavior, but it omits explanations for two parameters and does not describe the output format. Given that an output schema exists, the lack of return-value detail is acceptable, but the incomplete parameter context reduces 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 schema has three parameters, but only webhook_token has a description. request_id and filter_domain lack any description, and the tool description does not compensate for this gap—it only hints at 'defaults to the latest event' without explaining request_id's effect. With only 33% schema coverage and no meaningful explanation, parameter semantics are weak.

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 function: pulling confirm, reset, magic-link, and other URLs from a captured email or HTTP body. It also distinguishes this tool from siblings by noting that wait_for_email already extracts links and codes, implying this tool serves a different or more specific purpose.

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 explicitly says when to use the tool: after wait_for_email or get_webhook_requests when the user needs verification, login, or password-reset links or OTPs. It also mentions the default behavior of using the latest event, providing clear usage context.

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