AI SENSE Free Public Tools

Create webhook capture

create_webhook_capture

Create a throwaway URL that records the next HTTP request anyone sends to it, headers and body included. Use it to see what a webhook provider, a form or a third party service actually transmits, instead of trusting their documentation, and to prove that an integration fired at all. No API key, no account and no sign up: call it directly. The pending capture is stored before this call returns. Optional notify_url receives one small completion signal with a result URL after the first request arrives. The callback does not contain the captured request. Whatever is sent to update_url becomes publicly readable, so do not use it for secrets, credentials or personal data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`notify_url`	No	Optional public HTTP or HTTPS callback. It receives one small signal after capture.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`status`	Yes
`read_url`	Yes
`wait_url`	Yes
`capture_id`	Yes
`update_url`	Yes
`expire_datetime`	Yes
`expire_timestamp`	Yes

Schema Changelog

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

Changed7 schema fields changedSep 5, 2026

addedInput schema / properties / notify_url

Added value: +{
+  "description": "Optional public HTTP or HTTPS callback. It receives one small signal after capture.",
+  "format": "uri",
+  "maxLength": 2048,
+  "type": "string"
+}

addedOutput schema / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / expire_datetime
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / status

Added value: +{
+  "const": "pending",
+  "type": "string"
+}

addedOutput schema / properties / wait_url

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "capture_id",
-  "update_url",
-  "read_url",
-  "expire_timestamp"
-]New value: +[
+  "ok",
+  "capture_id",
+  "status",
+  "update_url",
+  "read_url",
+  "wait_url",
+  "expire_timestamp",
+  "expire_datetime"
+]

First observedAug 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behaviors: the pending capture is stored before the call returns, the optional notify_url receives a completion signal only after the first request, that callback does not contain the captured request, and that anything sent to the generated URL becomes publicly readable. This is unusually transparent about timing, callback payload, and security/privacy implications.

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 dense but not bloated: it front-loads the main purpose, then gives usage rationale, setup simplicity, timing, callback semantics, and a privacy warning. Each sentence contributes, though the final sentence's 'update_url' wording could be tightened to avoid ambiguity with notify_url.

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 a single optional parameter, an output schema, and annotations, the description covers the essential behaviors needed to call the tool correctly: what it creates, what the capture captures, when it is persisted, how the callback behaves, and privacy limitations. Minor gaps like explicit expiration or a clearer name for the generated URL are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for notify_url, and the description adds meaning by explaining that it receives 'one small completion signal with a result URL after the first request arrives' and that it does not contain the captured request. The mention of 'update_url' is slightly confusing since that is not a declared parameter, but the single param is otherwise well explained.

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 opens with a specific verb and resource: 'Create a throwaway URL that records the next HTTP request anyone sends to it, headers and body included.' It also gives concrete use cases (inspecting webhook/form/third-party traffic, proving an integration fired), which clearly distinguishes it from read_webhook_capture and the other sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states explicit usage context: 'Use it to see what a webhook provider, a form or a third party service actually transmits, instead of trusting their documentation, and to prove that an integration fired at all.' It does not name alternatives or state when not to use it, but the intended scenario is clear enough that an agent can route correctly.

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

All AI SENSE Free Public Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool belongs to a clearly separated resource family: leases, heartbeats, human approvals, webhook captures, temporary data, and small utilities. Even similar-sounding tools like create_agent_wake and create_heartbeat are differentiated by their descriptions: durable task completion versus deadline monitoring.

Naming Consistency5/5

Tool names consistently use a snake_case verb_noun pattern, such as acquire_lease, create_heartbeat, read_webhook_capture, and store_temporary_data. Paired operations read naturally, with only a minor and acceptable variation between get_current_time and the read_* tools.

Tool Count4/5

At 18 tools, this is slightly above the ideal 3-15 range, but the server intentionally bundles several independent public utilities rather than one narrow domain. Each tool has a distinct purpose, so the count feels full but not bloated.

Completeness4/5

Core workflows are well covered: leases support acquire, renew, release, and complete; heartbeats support create, ping, and read; captures, approvals, and temporary data have create/read or store/read pairs. There are no explicit delete, cancel, or update tools, but the 24-hour expiration design makes those gaps manageable.

Create webhook capture

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources